[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
sass	1.85.1 → 1.107.1

---

Release Notes

sass/dart-sass (sass)

v1.107.1

Compare Source

• Properly report the embedded protocol version as 3.4.0.

v1.107.0

Compare Source

Command-Line Interface

• The --fatal-deprecation flag can now exclude deprecations that would
  otherwise be included by passing a version number. To exclude a deprecation,
  add - before its name. For example, --fatal-deprecation=1.107.0,-import
  includes all deprecations that were present in Dart Sass 1.107.0 except for
  the @import deprecation.

• The --fatal-deprecation flag now takes the special value dart-sass-2,
  which treats as fatal all deprecations that will become fatal in Dart Sass
  2.0.0.

JavaScript API

• Options.fatalDeprecations can now take a DeprecationSelectorDifference
  object of the form {include: ..., except: ...}, where the include field
  lists deprecations to mark fatal (which can be version numbers) and the
  except field lists deprecations not to mark fatal. The except field
  takes precedence over include.

• Add a (non-enumerable) sass.deprecations.dartSass2 property which can be
  passed to Options.fatalDeprecations to mark as fatal exactly the
  deprecations that will become fatal in Dart Sass 2.0.0. This can be combined
  with other deprecations or used in a DeprecationSelectorDifference to modify
  exactly which deprecations it covers.

• Passing a version number beyond the current Dart Sass version to
  Options.fatalDeprecations is now deprecated. See the Sass
  website for details.

Dart API

• Add a Deprecation.dartSass2 property which returns exactly the set of
  deprecations that will become fatal in Dart Sass 2.0.0.

• Passing a version number beyond the current Dart Sass version to
  Deprecation.forVersion is now deprecated.

Embedded Protocol

• Add a CompileRequest.fatal_deprecation_except field which excludes
  deprecations from being considered fatal if they would have been enabled by
  CompileRequest.fatal_deprecation.

v1.106.1

Compare Source

• Fix a bug where an attribute selector with an empty value (such as
  [class=""]) would crash when serializing.

• Don't crash when serializing a number with an empty unit. This is only
  possible through the JavaScript and Dart APIs or the embedded protocol.

Embedded Dart Sass

• More robustly convert invalid value errors into PARAMS errors.

v1.106.0

Compare Source

• Don't normalize CSS escapes in statement contexts that can contain
  interpolation. For example, @f\6Fo is now emitted as written rather than
  normalized to @foo.

• Fix a bug where quotes would be removed from attribute selector values that
  contained backslashes.

• Fix invalid source spans that could cause crashes when encountering a syntax
  error in selectors or media queries that also contain escape sequences.

• Fix a bug where the indented syntax parser would crash when parsing a file
  where the first statement was indented and appeared after the first line.

• Fix a bug that could cause crashes when encountering errors or warnings in
  interpolations that contain patterns like // */.

• Potentially breaking compatibility fix: CSS escape codes whose values are
  0, for Unicode surrogates, or greater than the maximum allowed code point are
  now consistently normalized to U+FFFD REPLACEMENT CHARACTER in expression
  contexts. Previously, in some cases these were instead normalized to the
  normalized form of the original escape sequence, which violates the principle
  that all escape sequences for identical values should be normalized the same
  way. In other cases, these would simply throw errors.

  As a special case, \0 on its own will continue to be normalized to \0 to
  support historical CSS hacks.

• Potentially breaking bug fix: Throw an error for mixins and functions that
  have rest parameters which are the same as normal parameters. Previously, the
  positional parameters wouldn't be accessible and calling such a mixin or
  function with a named argument would crash the compiler.

• Potentially breaking bug fix: Fix various cases where using a CSS escape
  code at the beginning of an identifier would change parsing behavior versus
  using the character directly.

• Potentially breaking bug fix: When a number's unit is ambiguous with a
  numeric exponent, the unit is now serialized as an escape code rather than a
  literal e to avoid being interpreted as an exponent by CSS.

• Potentially breaking bug fix: Don't parse a CSS escape code for U+45 LATIN
  CAPITAL LETTER E or U+65 LATIN LOWERCASE LETTER E as an exponent in
  @keyframes percentage selectors.

• Potentially breaking bug fix: Properly normalize underscores written as
  CSS escape codes in variable, mixin, and function names.

v1.105.2

Compare Source

Node.js Embedded Host

• Fix a deadlock when the async compiler fails to start.

v1.105.1

Compare Source

• Improve error messages for @extends across different media queries.

v1.105.0

Compare Source

• Add support for first-class modules. These can be accessed using the new
  meta.load() and meta.get-module() functions, and may be passed as the
  $module argument to numerous eisting sass:meta functions.

• Add the meta.css() mixin, which includes CSS from a first-class module.

JS API

• Add a SassModule class and a corresponding Value.assertModule() method.

Dart API

• Add a SassModule class and a corresponding Value.assertModule() method.

v1.104.1

Compare Source

• Fix a bug where loud comments before @use rules could be emitted multiple
  times under certain circumstances.

• Fix a bug in which an invalid selector at the end of an indented syntax
  stylesheet would cause the parser to crash instead of emitting a useful error
  message.

Command Line Interface

• Many-to-many compilations no longer compile any files that appear in the
  output directory if the output directory is also within the source directory.
  This fixes a bug where --watch mode could enter an infinite loop recompiling
  the same CSS file over and over.

• Sass now sets the modification time of output files to the time compilation
  started rather than the time it ended. This ensures that, if a source file
  is modified during compilation, --watch and --update mode will recompile
  the outputs to include the new source file contents.

v1.104.0

Compare Source

• Potentially breaking compatibility fix: Colors now convert the special
  values NaN and negative zero, as well as infinity and negative infinity for
  polar-hue channels, to 0 as per the CSS spec.

• The special value negative zero is now serialized as -0 instead of 0 for
  greater compatibility when using it in CSS calculations.

v1.103.1

Compare Source

• No user-visible changes.

v1.103.0

Compare Source

• Potentially breaking compatibility fix: Colors now preserve "analogous
  sets" of missing channels during conversions, per the CSS spec. For example,
  color.to-space(lch(50% none none), lab) now returns lab(50% none none)
  instead of lab(50% 0 0).

v1.102.0

Compare Source

• Use the 2.4 gamma transfer function for rec2020, as specified by the latest
  draft of CSS Color 4.

v1.101.7

Compare Source

• No user-visible changes.

v1.101.6

Compare Source

• No user-visible changes.

v1.101.5

Compare Source

• No user-visible changes.

v1.101.4

Compare Source

• Avoid emitting rgb() or rgba() functions with non-percent decimal
  channels. Older browsers only support integer values or (potentially decimal)
  percentages for these functions, so in order to preserve
  backwards-compatibility while retaining full precision for modern browsers,
  legacy colors that contain at least one non-integer channel will now use
  percentages for their channels (for example, rgb(0%, 100%, 50%) rather than
  rgb(0, 255, 127.5)).

• Fix a bug where the values of plain-CSS if() expressions were emitted using
  their meta.inspect() format rather than their CSS serialization format.

v1.101.3

Compare Source

• No user-visible changes.

v1.101.0

Compare Source

• Potentially breaking bug fix: The Node package importer now properly
  supports resolving import-only variants of Sass files declared in the
  exports, sass, and style fields of package.json. Previously, these
  files were ignored even when loaded via @import, so any code relying on
  loading module-system-only files this way may break.

v1.100.0

Compare Source

• Writing two compound selectors adjacent to one another without any whitespace
  between them, such as [class]a, is now deprecated. This was always an error
  in CSS and Sass only supported it by mistake.

  See the Sass website for
  details.

v1.99.0

Compare Source

• Add support for parent selectors (&) at the root of the document. These are
  emitted as-is in the CSS output, where they're interpreted as the scoping
  root.

• User-defined functions named calc or clamp are no longer forbidden. If
  such a function exists without a namespace in the current module, it will be
  used instead of the built-in calc() or clamp() function.

• User-defined functions whose names begin with - and end with -expression,
  -url, -and, -or, or -not are no longer forbidden. These were
  originally intended to match vendor prefixes, but in practice no vendor
  prefixes for these functions ever existed in real browsers.

• User-defined functions named EXPRESSION, URL, and ELEMENT, those that
  begin with - and end with -ELEMENT, as well as the same names with some
  lowercase letters are now deprecated, These are names conflict with plain CSS
  functions that have special syntax.

  See the Sass website for details.

• In a future release, calls to functions whose names begin with - and end
  with -expression and -url will no longer have special parsing. For now,
  these calls are deprecated if their behavior will change in the future.

  See the Sass website for details.

• Calls to functions whose names begin with - and end with -progid:... are
  deprecated.

  See the Sass website for details.

v1.98.0

Compare Source

Command-Line Interface

• Gracefully handle dependency loops in --watch mode.

Dart API

• Add a const Logger.defaultLogger field. This provides a logger that emits to
  standard error or the browser console, but automatically chooses whether to
  use terminal colors.

JavaScript API

• Fix a crash when manually constructing a SassCalculation for 'calc' with
  an argument that can't be simplified.

• Properly emit deprecation warnings as text rather than StringBuffer objects
  when running in a browser.

• Emit colored warnings and other messages on the console when running in a
  browser.

v1.97.3

Compare Source

• Fix a bug where nesting an at-rule within multiple style rules in plain CSS
  could cause outer style rules to be omitted.

v1.97.2

Compare Source

• Additional fixes for implicit configuration when nested imports are involved.

v1.97.1

Compare Source

• Fix a bug with the new CSS-style if() syntax where values would be evaluated
  even if their conditions didn't match.

v1.97.0

Compare Source

• Add support for the display-p3-linear color space.

v1.96.0

Compare Source

• Allow numbers with complex units (more than one numerator unit or more than
  zero denominator units) to be emitted to CSS. These are now emitted as
  calc() expressions, which now support complex units in plain CSS.

v1.95.1

Compare Source

• No user-visible changes.

v1.95.0

Compare Source

• Add support for the CSS-style if() function. In addition to supporting the
  plain CSS syntax, this also supports a sass() query that takes a Sass
  expression that evaluates to true or false at preprocessing time depending
  on whether the Sass value is truthy. If there are no plain-CSS queries, the
  function will return the first value whose query returns true during
  preprocessing. For example, if(sass(false): 1; sass(true): 2; else: 3)
  returns 2.

• The old Sass if() syntax is now deprecated. Users are encouraged to migrate
  to the new CSS syntax. if($condition, $if-true, $if-false) can be changed to
  if(sass($condition): $if-true; else: $if-false).

  See the Sass website for details.

• Plain-CSS if() functions are now considered "special numbers", meaning that
  they can be used in place of arguments to CSS color functions.

• Plain-CSS if() functions and attr() functions are now considered "special
  variable strings" (like var()), meaning they can now be used in place of
  multiple arguments or syntax fragments in various CSS functions.

v1.94.3

Compare Source

• Fix the span reported for standalone % expressions followed by whitespace.

v1.94.2

Compare Source

Command-Line Interface

• Using --fatal-deprecation <version> no longer emits warnings about
  deprecations that are obsolete.

Dart API

• Deprecation.forVersion now excludes obsolete deprecations from the set it
  returns.

JS API

• Excludes obsolete deprecations from fatalDeprecations when a Version is
  passed.

Node.js Embedded Host

• Fix a bug where a variable could be used before it was initialized during
  async compilation.

v1.94.1

Compare Source

• No user-visible changes.

v1.94.0

Compare Source

• Potentially breaking compatibility fix: @function rules whose names
  begin with -- are now parsed as unknown at-rules to support the plain CSS
  @function rule. Within this rule, the result property is parsed as raw
  CSS just like custom properties.

• Potentially breaking compatibility fix: @mixin rules whose names begin
  with -- are now errors. These are not yet parsed as unknown at-rules because
  no browser currently supports CSS mixins.

v1.93.3

Compare Source

• Fix a performance regression that was introduced in 1.92.0.

v1.93.2

Compare Source

• No user-visible changes.

JavaScript API

• Fix another error in the release process for @sass/types.

v1.93.1

Compare Source

• No user-visible changes.

JavaScript API

• Fix an error in the release process for @sass/types.

v1.93.0

Compare Source

• Fix a crash when a style rule contains a nested @import, and the loaded file
  @uses a user-defined module as well as @includes a top-level mixin which
  emits top-level declarations.

JavaScript API

• Release a @sass/types package which contains the type annotations used by
  both the sass and sass-embedded package without any additional code or
  dependencies.

v1.92.1

Compare Source

• Fix a bug where variable definitions from one imported, forwarded module
  would not be passed as implicit configuration to a later imported, forwarded
  module.

v1.92.0

Compare Source

• Breaking change: Emit declarations, childless at-rules, and comments in
  the order they appear in the source even when they're interleaved with nested
  rules. This obsoletes the mixed-decls deprecation.

• Breaking change: The function name type() is now fully reserved for the
  plain CSS function. This means that @function definitions with the name
  type will produce errors, while function calls will be parsed as special
  function strings.

• Configuring private variables using @use ... with, @forward ... with, and
  meta.load-css(..., $with: ...) is now deprecated. Private variables were
  always intended to be fully encapsulated within the module that defines them,
  and this helps enforce that encapsulation.

• Fix a bug where @extend rules loaded through a mixture of @import and
  @use rules could fail to apply correctly.

Command-Line Interface

• In --watch mode, delete the source map when the associated source file is
  deleted.

v1.91.0

Compare Source

• Potentially breaking change: meta.inspect() (as well as other systems
  that use it such as @debug and certain error messages) now emits numbers
  with as high precision as is available instead of rounding to the nearest
  1e⁻¹⁰ as we do when serializing to CSS. This better fits the purpose of
  meta.inspect(), which is to provide full information about the structure of
  a Sass value.

• Passing a rest argument ($arg...) before a positional or named argument when
  calling a function or mixin is now deprecated. This was always outside the
  specified syntax, but it was historically treated the same as passing the rest
  argument at the end of the argument list whether or not that matched the
  visual order of the arguments.

v1.90.0

Compare Source

• Allow a @forwarded module to be loaded with a configuration when that module
  has already been loaded with a different configuration and the module
  doesn't define any variables that would have been configured anyway.

v1.89.2

Compare Source

Embedded Host

• Fixed a compilation error caused by an outdated buf dependency.

v1.89.1

Compare Source

• No user-visible changes.

v1.89.0

Compare Source

• Allow the Node package importer to load files even when there are multiple
  potential resolutions, as long as those resolutions all point to the same
  file.

v1.88.0

Compare Source

• Allow custom properties with empty values (such as --var:;).

• Fix a bug when calculating source spans for interpolations.

Dart and JS APIs

• Potentially breaking bug fix: Throw an error when passing a function or
  mixin object from one compilation to another.

Dart API

• Deprecate passing a relative URL to compileString() and related functions.

v1.87.0

Compare Source

• Potentially breaking bug fix: When a plain CSS file with a top-level
  nesting selector & is loaded into a nested Sass context via
  meta.load-css() or @import, Sass now emits plain CSS nesting rather than
  incorrectly combining it with the parent selector using a descendant
  combinator.

v1.86.3

Compare Source

• Fix a bug introduced in 1.86.1 where Sass fails to resolve paths starting with
  a .. segment.

v1.86.2

Compare Source

• No user-visible changes.

v1.86.1

Compare Source

• Improve the performance of file: URL case canonicalization on Windows and
  Mac OS.

v1.86.0

Compare Source

• Add support for % as an expression in its own right. It will still be parsed
  as the modulo operator when between two other expressions, but in any other
  context it will be an expression whose value is the unquoted string %.

• Consider attr() to be a special number function that can be used as a
  channel in color functions.

• Deprecate user-defined functions named type() so that we can eventually
  support the new CSS type() function.

Dart API

• Increase the minimum Dart SDK to 3.6.0.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.