Skip to content

Update sass npm from 1.49.9 to 1.69.0

Takuya Noguchi requested to merge tnir-update-sass-to-1.69.0 into master

What does this MR do and why?

Update sass npm from 1.49.9 to 1.69.0.

https://github.com/sass/dart-sass/blob/1.69.0/CHANGELOG.md

Full changelog

1.69.0

  • Add a meta.get-mixin() function that returns a mixin as a first-class Sass value.

  • Add a meta.apply() mixin that includes a mixin value.

  • Add a meta.module-mixins() function which returns a map from mixin names in a module to the first-class mixins that belong to those names.

  • Add a meta.accepts-content() function which returns whether or not a mixin value can take a content block.

  • Add support for the relative color syntax from CSS Color 5. This syntax cannot be used to create Sass color values. It is always emitted as-is in the CSS output.

Dart API

  • Deprecate Deprecation.calcInterp since it was never actually emitted as a deprecation.

Embedded Sass

  • Fix a rare race condition where the embedded compiler could freeze when a protocol error was immediately followed by another request.

1.68.0

  • Fix the source spans associated with the abs-percent deprecation.

JS API

  • Non-filesystem importers can now set the nonCanonicalScheme field, which declares that one or more URL schemes (without :) will never be used for URLs returned by the canonicalize() method.

  • Add a containingUrl field to the canonicalize() and findFileUrl() methods of importers, which is set to the canonical URL of the stylesheet that contains the current load. For filesystem importers, this is always set; for other importers, it's set only if the current load has no URL scheme, or if its URL scheme is declared as non-canonical by the importer.

Dart API

  • Add AsyncImporter.isNonCanonicalScheme, which importers (async or sync) can use to indicate that a certain URL scheme will never be used for URLs returned by the canonicalize() method.

  • Add AsyncImporter.containingUrl, which is set during calls to the canonicalize() method to the canonical URL of the stylesheet that contains the current load. This is set only if the current load has no URL scheme, or if its URL scheme is declared as non-canonical by the importer.

Embedded Sass

  • The CalculationValue.interpolation field is deprecated and will be removed in a future version. It will no longer be set by the compiler, and if the host sets it it will be treated as equivalent to CalculationValue.string except that "(" and ")" will be added to the beginning and end of the string values.

  • Properly include TypeScript types in the sass-embedded package.

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.

1.65.1

  • Update abs-percent deprecatedIn version to 1.65.0.

1.65.0

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

  • Deprecate explicitly passing the % unit to the global abs() function. In future releases, this will emit a CSS abs() function to be resolved by the browser. This deprecation is named abs-percent.

1.64.3

Dart API

  • Deprecate explicitly passing null as the alpha channel for SassColor.rgb(), SassColor.hsl(), and SassColor.hwb(). Omitting the alpha channel is still allowed. In future releases, null will be used to indicate a missing component. This deprecation is named null-alpha.

  • Include protocol buffer definitions when uploading the sass package to pub.

JS API

  • Deprecate explicitly passing null as the alpha channel for new SassColor(). Omitting the alpha channel or passing undefined for it is still allowed. In future releases, null will be used to indicate a missing component. This deprecation is named null-alpha.

    (Note that this was already prohibited by the TypeScript types, but in practice prior to this null was treated as 1.)

1.64.2

  • No user-visible changes.

1.64.1

Embedded Sass

  • Fix a bug where a valid SassCalculation.clamp() with less than 3 arguments would throw an error.

1.64.0

  • Comments that appear before or between @use and @forward rules are now emitted in source order as much as possible, instead of always being emitted after the CSS of all module dependencies.

  • Fix a bug where an interpolation in a custom property name crashed if the file was loaded by a @use nested in an @import.

JavaScript API

  • Add a new SassCalculation type that represents the calculation objects added in Dart Sass 1.40.0.

  • Add Value.assertCalculation(), which returns the value if it's a SassCalculation and throws an error otherwise.

  • Produce a better error message when an environment that supports some Node.js APIs loads the browser entrypoint but attempts to access the filesystem.

Embedded Sass

  • Fix a bug where nested relative @imports failed to load when using the deprecated functions render or renderSync and those relative imports were loaded multiple times across different files.

1.63.6

JavaScript API

  • Fix import sass from 'sass' again after it was broken in the last release.

Embedded Sass

  • Fix the exports declaration in package.json.

1.63.5

JavaScript API

  • Fix a bug where loading the package through both CJS require() and ESM import could crash on Node.js.

Embedded Sass

  • Fix a deadlock when running at high concurrency on 32-bit systems.

  • Fix a race condition where the embedded compiler could deadlock or crash if a compilation ID was reused immediately after the compilation completed.

1.63.4

JavaScript API

  • Re-enable support for import sass from 'sass' when loading the package from an ESM module in Node.js. However, this syntax is now deprecated; ESM users should use import * as sass from 'sass' instead.

    On the browser and other ESM-only platforms, only import * as sass from 'sass' is supported.

  • Properly export the legacy API values TRUE, FALSE, NULL, and types from the ECMAScript module API.

Embedded Sass

  • Fix a race condition where closing standard input while requests are in-flight could sometimes cause the process to hang rather than shutting down gracefully.

  • Properly include the root stylesheet's URL in the set of loaded URLs when it fails to parse.

1.63.3

JavaScript API

  • Fix loading Sass as an ECMAScript module on Node.js.

1.63.2

  • No user-visible changes.

1.63.1

  • No user-visible changes.

1.63.0

JavaScript API

  • Dart Sass's JS API now supports running in the browser. Further details and instructions for use are in the README.

Embedded Sass

  • The Dart Sass embedded compiler is now included as part of the primary Dart Sass distribution, rather than a separate executable. To use the embedded compiler, just run sass --embedded from any Sass executable (other than the pure JS executable).

    The Node.js embedded host will still be distributed as the sass-embedded package on npm. The only change is that it will now provide direct access to a sass executable with the same CLI as the sass package.

  • The Dart Sass embedded compiler now uses version 2.0.0 of the Sass embedded protocol. See the spec for a full description of the protocol, and the changelog for a summary of changes since version 1.2.0.

  • The Dart Sass embedded compiler now runs multiple simultaneous compilations in parallel, rather than serially.

1.62.1

  • Fix a bug where :has(+ &) and related constructs would drop the leading combinator.

1.62.0

  • Deprecate the use of multiple !global or !default flags on the same variable. This deprecation is named duplicate-var-flags.

  • Allow special numbers like var() or calc() in the global functions: grayscale(), invert(), saturate(), and opacity(). These are also native CSS filter functions. This is in addition to number values which were already allowed.

  • Fix a cosmetic bug where an outer rule could be duplicated after nesting was resolved, instead of re-using a shared rule.

1.61.0

  • Potentially breaking change: Drop support for End-of-Life Node.js 12.

  • Fix remaining cases for the performance regression introduced in 1.59.0.

Embedded Sass

  • The JS embedded host now loads files from the working directory when using the legacy API.

1.60.0

  • Add support for the pi, e, infinity, -infinity, and NaN constants in calculations. These will be interpreted as the corresponding numbers.

  • Add support for unknown constants in calculations. These will be interpreted as unquoted strings.

  • Serialize numbers with value infinity, -infinity, and NaN to calc() expressions rather than CSS-invalid identifiers. Numbers with complex units still can't be serialized.

1.59.3

  • Fix a performance regression introduced in 1.59.0.

  • The NPM release of 1.59.0 dropped support for Node 12 without actually indicating so in its pubspec. This release temporarily adds back support so that the latest Sass version that declares it supports Node 12 actually does so. However, Node 12 is now end-of-life, so we will drop support for it properly in an upcoming release.

1.59.2

  • No user-visible changes.

1.59.1

  • No user-visible changes.

1.59.0

Command Line Interface

  • Added a new --fatal-deprecation flag that lets you treat a deprecation warning as an error. You can pass an individual deprecation ID (e.g. slash-div) or you can pass a Dart Sass version to treat all deprecations initially emitted in that version or earlier as errors.

  • New --future-deprecation flag that lets you opt into warning for use of certain features that will be deprecated in the future. At the moment, the only option is --future-deprecation=import, which will emit warnings for Sass @import rules, which are not yet deprecated, but will be in the future.

Dart API

  • New Deprecation enum, which contains the different current and future deprecations used by the new CLI flags.

  • The compile methods now take in fatalDeprecations and futureDeprecations parameters, which work similarly to the CLI flags.

1.58.4

  • Pull @font-face to the root rather than bubbling the style rule selector inwards.

  • Improve error messages for invalid CSS values passed to plain CSS functions.

  • Improve error messages involving selectors.

Embedded Sass

  • Improve the performance of starting up a compilation.

1.58.3

  • No user-visible changes.

1.58.2

Command Line Interface

  • Add a timestamp to messages printed in --watch mode.

  • Print better calc()-based suggestions for /-as-division expression that contain calculation-incompatible constructs like unary minus.

1.58.1

  • Emit a unitless hue when serializing hsl() colors. The deg unit is incompatible with IE, and while that officially falls outside our compatibility policy, it's better to lean towards greater compatibility.

1.58.0

  • Remove sourcemap comments from Sass sources. The generated sourcemap comment for the compiled CSS output remains unaffected.

  • Fix a bug in @extend logic where certain selectors with three or more combinators were incorrectly considered superselectors of similar selectors with fewer combinators, causing them to be incorrectly trimmed from the output.

  • Produce a better error message for a number with a leading + or -, a decimal point, but no digits.

  • Produce a better error message for a nested property whose name starts with --.

  • Fix a crash when a selector ends in an escaped backslash.

  • Add the relative length units from CSS Values 4 and CSS Contain 3 as known units to validate bad computation in calc.

Command Line Interface

  • The --watch flag will now track loads through calls to meta.load-css() as long as their URLs are literal strings without any interpolation.

1.57.1

  • No user-visible changes.

1.57.0

  • Add a split($string, $separator, $limit: null) function to sass:string that splits a string into separate substrings based on a separator string.

JavaScript API

  • Potentially breaking bug fix: Custom functions in both the modern and legacy API now properly reject signatures with whitespace between the function name and parentheses.

  • Custom functions in the legacy API now allow signatures with whitespace before the function name, to match a bug in Node Sass.

Dart API

  • Potentially breaking bug fix: Callable.fromSignature() and AsyncCallable.fromSignature() now reject signatures with whitespace between the function name and parentheses.

1.56.2

Embedded Sass

1.56.1

Embedded Sass

  • Importer results now validate that contents is actually a string and whether sourceMapUrl is an absolute URL.

1.56.0

  • Potentially breaking change: To match the CSS spec, SassScript expressions beginning with not or ( are no longer supported at the beginning of parenthesized sections of media queries. For example,

    @media (width >= 500px) and (not (grid))

    will now be emitted unchanged, instead of producing

    @media (width >= 500px) and (false)

    See the Sass website for details.

  • Potentially breaking bug fix: Angle units like rad or turn are now properly converted to equivalent deg values for hsl(), hsla(), adjust-hue(), color.adjust(), and color.change().

    See the Sass website for details.

  • Fix indentation for selectors that span multiple lines in a @media query.

  • Emit a deprecation warning when passing $alpha values with units to color.adjust() or color.change(). This will be an error in Dart Sass 2.0.0.

    See the Sass website for details.

  • Emit a deprecation warning when passing a $weight value with no units or with units other than % to color.mix(). This will be an error in Dart Sass 2.0.0.

    See the Sass website for details.

  • Emit a deprecation warning when passing $n values with units to list.nth() or list.set-nth(). This will be an error in Dart Sass 2.0.0.

    See the Sass website for details.

  • Improve existing deprecation warnings to wrap /-as-division suggestions in calc() expressions.

  • Properly mark the warning for passing numbers with units to random() as a deprecation warning.

  • Fix a bug where @extend could behave unpredicatably when used along with meta.load-css() and shared modules that contained no CSS themselves but loaded CSS from other modules.

Dart API

  • Emit a deprecation warning when passing a sassIndex with units to Value.sassIndexToListIndex(). This will be an error in Dart Sass 2.0.0.

JS API

  • Importer results now validate whether contents is actually a string type.

  • Importer result argument errors are now rendered correctly.

1.55.0

  • Potentially breaking bug fix: Sass numbers are now universally stored as 64-bit floating-point numbers, rather than sometimes being stored as integers. This will generally make arithmetic with very large numbers more reliable and more consistent across platforms, but it does mean that numbers between nine quadrillion and nine quintillion will no longer be represented with full accuracy when compiling Sass on the Dart VM.

  • Potentially breaking bug fix: Sass equality is now properly transitive. Two numbers are now considered equal (after doing unit conversions) if they round to the same 1e-11th. Previously, numbers were considered equal if they were within 1e-11 of one another, which led to some circumstances where $a == $b and $b == $c but $a != $b.

  • Potentially breaking bug fix: Various functions in sass:math no longer treat floating-point numbers that are very close (but not identical) to integers as integers. Instead, these functions now follow the floating-point specification exactly. For example, math.pow(0.000000000001, -1) now returns 1000000000000 instead of Infinity.

  • Emit a deprecation warning for $a -$b and $a +$b, since these look like they could be unary operations but they're actually parsed as binary operations. Either explicitly write $a - $b or $a (-$b). See https://sass-lang.com/d/strict-unary for more details.

Dart API

  • Add an optional argumentName parameter to SassScriptException() to make it easier to throw exceptions associated with particular argument names.

  • Most APIs that previously returned num now return double. All APIs continue to accept num, although in Dart 2.0.0 these APIs will be changed to accept only double.

JS API

  • Fix a bug in which certain warning spans would not have their properties accessible by the JS API.

1.54.9

  • Fix an incorrect span in certain @media query deprecation warnings.

1.54.8

  • No user-visible changes.

1.54.7

  • Add support for 32-bit ARM releases on Linux.

1.54.6

  • Fix a bug where a @media query could be incorrectly omitted from a stylesheet if it had multiple levels of nested @media queries within it and the inner queries were mergeable but the outer query was not.

1.54.5

  • Properly consider a ~ c to be a superselector of a ~ b ~ c and a + b + c.

  • Properly consider b > c to be a superselector of a > b > c, and similarly for other combinators.

  • Properly calculate specificity for selector pseudoclasses.

  • Deprecate use of random() when $limit has units to make it explicit that random() currently ignores units. A future version will no longer ignore units.

  • Don't throw an error when the same module is @forwarded multiple times through a configured module.

Embedded Sass

  • Rather than downloading the embedded compiler for the local platform on install, the sass-embedded npm package now declares optional dependencies on platform-specific embedded compiler packages.

1.54.4

  • Improve error messages when passing incorrect units that are also out-of-bounds to various color functions.

1.54.3

  • Release a native ARM64 executable for Mac OS.

1.54.2

  • No user-visible changes.

1.54.1

  • When unifying selectors for @extend and selector.unify(), ensure that :root, :scope, :host, and :host-context only appear at the beginning of complex selectors.

1.54.0

  • Deprecate selectors with leading or trailing combinators, or with multiple combinators in a row. If they're included in style rules after nesting is resolved, Sass will now produce a deprecation warning and, in most cases, omit the selector. Leading and trailing combinators can still be freely used for nesting purposes.

    See https://sass-lang.com/d/bogus-combinators for more details.

  • Add partial support for new media query syntax from Media Queries Level 4. The only exception are logical operations nested within parentheses, as these were previously interpreted differently as SassScript expressions.

    A parenthesized media condition that begins with not or an opening parenthesis now produces a deprecation warning. In a future release, these will be interpreted as plain CSS instead.

  • Deprecate passing non-deg units to color.hwb()'s $hue argument.

  • Fix a number of bugs when determining whether selectors with pseudo-elements are superselectors.

  • Treat * as a superselector of all selectors.

Dart API

  • Add a top-level fakeFromImport() function for testing custom importers that use AsyncImporter.fromImport.

JS API

  • Add a charset option that controls whether or not Sass emits a @charset/BOM for non-ASCII stylesheets.

  • Fix Sass npm package types for TS 4.7+ Node16 and NodeNext module resolution.

1.53.0

  • Add support for calling var() with an empty second argument, such as var(--side, ).

JS API

  • Fix a bug where meta.load-css() would sometimes resolve relative URLs incorrectly when called from a mixin using the legacy JS API.

Embedded Sass

  • Respect npm's proxy settings when downloading the embedded Sass compiler.

1.52.3

  • Fix crash when trailing loud comments (/* ... */) appear twice in a row across two different imports which themselves imported the same file each.

1.52.2

  • Preserve location of trailing loud comments (/* ... */) instead of pushing the comment to the next line.

1.52.1

Command Line Interface

  • Fix a bug where --watch mode would close immediately in TTY mode. This was caused by our change to close --watch when stdin was closed outside of TTY mode, which has been reverted for now while we work on a fix.

1.52.0

  • Add support for arbitrary modifiers at the end of plain CSS imports, in addition to the existing supports() and media queries. Sass now allows any sequence of identifiers of functions after the URL of an import for forwards compatibility with future additions to the CSS spec.

  • Fix an issue where source locations tracked through variable references could potentially become incorrect.

  • Fix a bug where a loud comment in the source can break the source map when embedding the sources, when using the command-line interface or the legacy JS API.

JS API

  • SassNumber.assertUnit() and SassNumber.assertNoUnits() now correctly return the number called on when it passes the assertion.

1.51.0

  • Potentially breaking change: Change the order of maps returned by map.deep-merge() to match those returned by map.merge(). All keys that appeared in the first map will now be listed first in the same order they appeared in that map, followed by any new keys added from the second map.

  • Improve the string output of some AST nodes in error messages.

1.50.1

Embedded Sass

  • The JS embedded host and the embedded compiler will now properly avoid resolving imports relative to the current working directory unless '.' is passed as a load path.

  • Fix a bug in the JS embedded host's implementation of the legacy JS API where imports that began with / could crash on Windows.

1.50.0

  • @extend now treats :where() the same as :is().

Command Line Interface

  • Closing the standard input stream will now cause the --watch command to stop running.

Embedded Sass

  • Fix a bug where the JS embedded host crashed when invoking a legacy importer after resolving a relative filesystem import.

  • Improve error messages when returning non-Object values from legacy importers.

1.49.11

  • Add support for 64-bit ARM releases on Linux.

Embedded Sass

  • The embedded compiler now correctly sets the id field for all OutboundMessages.

1.49.10

  • Quiet deps mode now silences compiler warnings in mixins and functions that are defined in dependencies even if they're invoked from application stylesheets.

  • In expanded mode, Sass will now emit colors using rgb(), rbga(), hsl(), and hsla() function notation if they were defined using the corresponding notation. As per our browser support policy, this change was only done once 95% of browsers were confirmed to support this output format, and so is not considered a breaking change.

    Note that this output format is intended for human readability and not for interoperability with other tools. As always, Sass targets the CSS specification, and any tool that consumes Sass's output should parse all colors that are supported by the CSS spec.

  • Fix a bug in which a color written using the four- or eight-digit hex format could be emitted as a hex color rather than a format with higher browser compatibility.

  • Calculations are no longer simplified within supports declarations

Screenshots or screen recordings

n/a

How to set up and validate locally

  • yarn && bin/rake assets:precompile

MR acceptance checklist

Previous update

Signed-off-by: Takuya Noguchi takninnovationresearch@gmail.com

Edited by Takuya Noguchi

Merge request reports