sass-embedded-darwin-x64 - npm Package Versions

1.69.7

Embedded Sass

• In the JS Embedded Host, properly install the x64 Dart Sass executable on ARM64 Windows.

1.69.6

• Produce better output for numbers with complex units in meta.inspect() and debugging messages.

• Escape U+007F DELETE when serializing strings.

• When generating CSS error messages to display in-browser, escape all code points that aren't in the US-ASCII region. Previously only code points U+0100 LATIN CAPITAL LETTER A WITH MACRON were escaped.

• Provide official releases for musl LibC and for Android.

• Don't crash when running meta.apply() in asynchronous mode.

JS API

• Fix a bug where certain exceptions could produce SourceSpans that didn't follow the documented SourceSpan API.

1.69.5

JS API

• Compatibility with Node.js 21.0.0.

1.69.4

• No user-visible changes.

1.69.3

Embedded Sass

• Fix TypeScript type locations in package.json.

1.69.2

JS API

• Fix a bug where Sass crashed when running in the browser if there was a global variable named process.

1.69.1

• No user-visible changes.

1.67.0

• All functions defined in CSS Values and Units 4 are now once again parsed as calculation objects: round(), mod(), rem(), sin(), cos(), tan(), asin(), acos(), atan(), atan2(), pow(), sqrt(), hypot(), log(), exp(), abs(), and sign().

  Unlike in 1.65.0, function calls are not locked into being parsed as calculations or plain Sass functions at parse-time. This means that user-defined functions will take precedence over CSS calculations of the same name. Although the function names calc() and clamp() are still forbidden, users may continue to freely define functions whose names overlap with other CSS calculations (including abs(), min(), max(), and round() whose names overlap with global Sass functions).

• Breaking change: As a consequence of the change in calculation parsing described above, calculation functions containing interpolation are now parsed more strictly than before. However, almost all interpolations that would have produced valid CSS will continue to work. The only exception is #{$variable}% which is not valid in Sass and is no longer valid in calculations. Instead of this, either use $variable directly and ensure it already has the % unit, or write ($variable * 1%).

• Potentially breaking bug fix: The importer used to load a given file is no longer used to load absolute URLs that appear in that file. This was unintented behavior that contradicted the Sass specification. Absolute URLs will now correctly be loaded only from the global importer list. This applies to the modern JS API, the Dart API, and the embedded protocol.

Embedded Sass

• Substantially improve the embedded compiler's performance when compiling many files or files that require many importer or function call round-trips with the embedded host.

1.66.1

JS API

• Fix a bug where Sass compilation could crash in strict mode if passed a callback that threw a string, boolean, number, symbol, or bignum.

1.66.0

• Breaking change: Drop support for the additional CSS calculations defined in CSS Values and Units 4. Custom Sass functions whose names overlapped with these new CSS functions were being parsed as CSS calculations instead, causing an unintentional breaking change outside our normal [compatibility policy] for CSS compatibility changes.

  Support will be added again in a future version, but only after Sass has emitted a deprecation warning for all functions that will break for at least three months prior to the breakage.