chore(deps): update dependency sass to v1.49.9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
sass	1.32.12 -> 1.49.9

---

Release Notes

sass/dart-sass

v1.49.9

Compare Source

Embedded Sass

• Fixed a bug where the legacy API could crash when passed an empty importer
  list.

v1.49.8

Compare Source

• Fixed a bug where some plain CSS imports would not be emitted.

JS API

• Fix a bug where inspecting the Sass module in the Node.js console crashed on
  Node 17.

Embedded Sass

• Fix a bug where source map URLs were incorrectly generated when passing
  importers to the legacy API.

v1.49.7

Compare Source

Embedded Sass

• First stable release the sass-embedded npm package that contains the Node.js
  Embedded Host.

• First stable release of the sass_embedded pub package that contains the
  Embedded Dart Sass compiler.

v1.49.6

Compare Source

• No user-visible changes.

v1.49.5

Compare Source

• No user-visible changes.

v1.49.4

Compare Source

• No user-visible changes.

v1.49.3

Compare Source

• No user-visible changes.

v1.49.2

Compare Source

• No user-visible changes.

v1.49.1

Compare Source

• Stop supporting non-LTS Node.js versions.

v1.49.0

Compare Source

• Fix a bug in string.insert with certain negative indices.

JS API

• Add support for the sourceMapIncludeSources option in the new JS API.

TypeScript Declarations

• Fix a bug where LegacyPluginThis.options.linefeed was typed to return
  abbreviations when it actually returned literal linefeed characters.

v1.48.0

Compare Source

JS API

• Potentially breaking bug fix: Match the specification of the new JS API by
  setting LegacyResult.map to undefined rather than null.

TypeScript Declarations

• Add a declaration for the NULL constant.

v1.47.0

Compare Source

JS API

TypeScript Declarations

• Add declarations for the TRUE and FALSE constants.

v1.46.0

Compare Source

JS API

• Potentially breaking bug fix: Match the specification of the new JS API by
  passing undefined rather than null to Logger.warn() for an unset span.

TypeScript Declarations

• Add a declaration for the LegacyPluginThis.options.context field.

• Update the definition of LegacyAsyncFunction to include explicit definitions
  with zero through six arguments before the done parameter. This makes it
  possible for TypeScript users to pass in callbacks that take a specific number
  of arguments, rather than having to declare a callback that takes an arbitrary
  number.

• Add a declaration for types.Error, a legacy API class that can be returned
  by asynchronous functions to signal asynchronous errors.

• Add a LegacyAsyncFunctionDone type for the done callback that's passed to
  LegacyAsyncFunction.

v1.45.2

Compare Source

JS API

• Potentially breaking bug fix: Change the default value of the separator
  parameter for new SassArgumentList() to ',' rather than null. This
  matches the API specification.

v1.45.1

Compare Source

• Potentially breaking bug fix: Properly parse custom properties in
  @supports conditions. Note that this means that SassScript expressions on
  the right-hand side of custom property @supports queries now need to be
  interpolated, as per https://sass-lang.com/d/css-vars.

• Potentially breaking bug fix: Fix a bug where inspect() was not
  properly printing nested, empty, bracketed lists.

v1.45.0

Compare Source

JS API

This release includes an entirely new JavaScript API, designed to be more
idiomatic, performant, and usable. The old API will continue to be supported
until Dart Sass 2.0.0, but it is now considered deprecated and should be avoided
for new code.

The new API includes:

• compile() and compileAsync() functions that take Sass file paths and
  return the result of compiling them to CSS. The async function returns a
  Promise rather than using a callback-based API.

• compileString() and compileStringAsync() functions that take a string of
  Sass source and compiles it to CSS. As above, the async function returns a
  Promise.

• A new importer API that more closely matches the Sass specification's logic
  for resolving loads. This makes it much easier for Sass to cache information
  across @import and @use rules, which substantially improves performance
  for applications that rely heavily on repeated @imports.

• A new custom function API, including much more usable JS representations of
  Sass value types complete with type-assertion functions, easy map and list
  lookups, and compatibility with the [immutable][immutable] package. Unlike in the
  legacy API, function callbacks now take one argument which contains an array
  of Sass values (rather than taking a separate JS argument for each Sass
  argument).

For full documentation of this API, please see the Sass website.

This release also adds TypeScript type definitions.

v1.44.0

Compare Source

• Suggest calc() as an alternative in /-as-division deprecation messages.

Dart API

• Add SassNumber.convert() and SassNumber.convertValue(). These work like
  SassNumber.coerce() and SassNumber.coerceValue(), except they don't treat
  unitless numbers as universally compatible.

• Fix a bug where SassNumber.coerceToMatch() and
  SassNumber.coerceValueToMatch() wouldn't coerce single-unit numbers to
  match unitless numbers.

v1.43.5

Compare Source

• Fix a bug where calculations with different operators were incorrectly
  considered equal.

• Properly parse attribute selectors with empty namespaces.

JS API

• Print more detailed JS stack traces. This is mostly useful for the Sass team's
  own debugging purposes.

v1.43.4

Compare Source

JS API

• Fix a bug where the logger option was ignored for the render() function.

v1.43.3

Compare Source

• Improve performance.

v1.43.2

Compare Source

• Improve the error message when the default namespace of a @use rule is not
  a valid identifier.

v1.42.1

Compare Source

• Fix a bug where Sass variables and function calls in calculations weren't
  being resolved correctly if there was a parenthesized interpolation elsewhere
  in the file.

v1.42.0

Compare Source

• min() and max() expressions are once again parsed as calculations as long
  as they contain only syntax that's allowed in calculation expressions. To
  avoid the backwards-compatibility issues that were present in 1.40.0, they now
  allow unitless numbers to be mixed with numbers with units just like the
  global min() and max() functions. Similarly, + and - operations within
  min() and max() functions allow unitless numbers to be mixed with numbers
  with units.

v1.41.1

Compare Source

• Preserve parentheses around var() functions in calculations, because they
  could potentially be replaced with sub-expressions that might need to be
  parenthesized.

v1.41.0

Compare Source

• Calculation values can now be combined with strings using the + operator.
  This was an error in 1.40.0, but this broke stylesheets that were relying on
  $value + "" expressions to generically convert values to strings. (Note that
  the Sass team recommends the use of "#{$value}" or inspect($value) for
  that use-case.)

• The selector.unify() function now correctly returns null when one selector
  is a :host or :host-context and the other is a selector that's guaranteed
  to be within the current shadow DOM. The @extend logic has been updated
  accordingly as well.

• Fix a bug where extra whitespace in min(), max(), clamp(), and calc()
  expressions could cause bogus parse errors.

• Fix a bug where the right-hand operand of a - in a calculation could
  incorrectly be stripped of parentheses.

Dart API

• SassCalculation.plus() now allows SassString arguments.

v1.40.1

Compare Source

• Potentially breaking bug fix: min() and max() expressions outside of
  calculations now behave the same way they did in 1.39.2, returning unquoted
  strings if they contain no Sass-specific features and calling the global
  min() and max() functions otherwise. Within calculations, they continue to
  behave how they did in 1.40.0.

  This fixes an unintended breaking change added in 1.40.0, wherein passing a
  unitless number and a number without units to min() or max() now produces
  an error. Since this breakage affects a major Sass library, we're temporarily
  reverting support for min() and max() calculations while we work on
  designing a longer-term fix.

v1.40.0

Compare Source

• Add support for first-class calc() expressions (as well as clamp() and
  plain-CSS min() and max()). This means:

  • calc() expressions will be parsed more thoroughly, and errors will be
    highlighted where they weren't before. This may break your stylesheets,
    but only if they were already producing broken CSS.

  • calc() expressions will be simplified where possible, and may even return
    numbers if they can be simplified away entirely.

  • calc() expressions that can't be simplified to numbers return a new data
    type known as "calculations".

  • Sass variables and functions can now be used in calc() expressions.

  • New functions meta.calc-name() and meta.calc-args() can now inspect
    calculations.

Dart API

• Add a new value type, SassCalculation, that represents calculations.

• Add new CalculationOperation, CalculationOperator, and
  CalculationInterpolation types to represent types of arguments that may
  exist as part of a calculation.

• Add a new Value.assertCalculation() method.

• Add a new Number.hasCompatibleUnits() method.

v1.39.2

Compare Source

• Fix a bug where configuring with @use ... with would throw an error when
  that variable was defined in a module that also contained @forward ... with.

v1.39.1

Compare Source

• Partial fix for a bug where @at-root does not work properly in nested
  imports that contain @use rules. If the only @use rules in the nested
  import are for built-in modules, @at-root should now work properly.

v1.39.0

Compare Source

JS API

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

v1.38.2

Compare Source

• No user-visible changes

v1.38.1

Compare Source

• No user-visible changes

v1.38.0

Compare Source

• In expanded mode, emit characters in Unicode private-use areas as escape
  sequences rather than literal characters.

• Fix a bug where quotes would be omitted for an attribute selector whose value
  was a single backslash.

• Properly consider numbers that begin with . as "plain CSS" for the purposes
  of parsing plain-CSS min() and max() functions.

• Allow if to be used as an unquoted string.

• Properly parse backslash escapes within url() expressions.

• Fix a couple bugs where @extends could be marked as unsatisfied when
  multiple identical @extends extended selectors across @use rules.

Command Line Interface

• Strip CRLF newlines from snippets of the original stylesheet that are included
  in the output when an error occurs.

JS API

• Don't crash when a Windows path is returned by a custom Node importer at the
  same time as file contents.

• Don't crash when an error occurs in a stylesheet loaded via a custom importer
  with a custom URL scheme.

Dart API

• Add a SassArgumentList.keywordsWithoutMarking getter to access the keyword
  arguments of an argument list without marking them accessed.

v1.37.5

Compare Source

• No user-visible changes.

v1.37.4

Compare Source

• No user-visible changes.

v1.37.3

Compare Source

• No user-visible changes.

v1.37.2

Compare Source

• No user-visible changes.

v1.37.1

Compare Source

• No user-visible changes.

v1.37.0

Compare Source

Dart API

• Potentially breaking bug fix: SassNumber.asSlash,
  SassNumber.withSlash(), and SassNumber.withoutSlash() have been marked as
  @internal. They were never intended to be used outside the sass package.

• Potentially breaking bug fix: SassException has been marked as @sealed
  to formally indicate that it's not intended to be extended outside of the
  sass package.

• Add a Value.withListContents() method that returns a new Sass list with the
  same list separator and brackets as the current value, interpreted as a list.

v1.36.0

Compare Source

Dart API

• Added compileToResult(), compileStringToResult(),
  compileToResultAsync(), and compileStringToResultAsync() methods. These
  are intended to replace the existing compile*() methods, which are now
  deprecated. Rather than returning a simple string, these return a
  CompileResult object, which will allow us to add additional information
  about the compilation without having to introduce further deprecations.

  • Instead of passing a sourceMaps callback to compile*(), pass
    sourceMaps: true to compile*ToResult() and access
    CompileResult.sourceMap.

  • The CompileResult object exposes a loadedUrls object which lists the
    canonical URLs accessed during a compilation. This information was
    previously unavailable except through the JS API.

v1.35.2

Compare Source

• Potentially breaking bug fix: Properly throw an error for Unicode ranges
  that have too many ?s after hexadecimal digits, such as U+12345??.

• Potentially breaking bug fix: Fixed a bug where certain local variable
  declarations nested within multiple @if statements would incorrectly
  override a global variable. It's unlikely that any real stylesheets were
  relying on this bug, but if so they can simply add !global to the variable
  declaration to preserve the old behavior.

• Potentially breaking bug fix: Fix a bug where imports of root-relative
  URLs (those that begin with /) in @import rules would be passed to
  both Dart and JS importers as file: URLs.

• Properly support selector lists for the $extendee argument to
  selector.extend() and selector.replace().

• Fix an edge case where @extend wouldn't affect a selector within a
  pseudo-selector such as :is() that itself extended other selectors.

• Fix a race condition where meta.load-css() could trigger an internal error
  when running in asynchronous mode.

Dart API

• Use the @internal annotation to indicate which Value APIs are available
  for public use.

v1.35.1

Compare Source

• Fix a bug where the quiet dependency flag didn't silence warnings in some
  stylesheets loaded using @import.

v1.35.0

Compare Source

• Fix a couple bugs that could prevent some members from being found in certain
  files that use a mix of imports and the module system.

• Fix incorrect recommendation for migrating division expressions that reference
  namespaced variables.

JS API

• Add a quietDeps option which silences compiler warnings from stylesheets
  loaded through importers and load paths.

• Add a verbose option which causes the compiler to emit all deprecation
  warnings, not just 5 per feature.

v1.34.1

Compare Source

• Fix a bug where --update would always compile any file that depends on a
  built-in module.

• Fix the URL for the @-moz-document deprecation message.

• Fix a bug with @for loops nested inside property declarations.

v1.34.0

Compare Source

• Don't emit the same warning in the same location multiple times.

• Cap deprecation warnings at 5 per feature by default.

Command Line Interface

• Add a --quiet-deps flag which silences compiler warnings from stylesheets
  loaded through --load-paths.

• Add a --verbose flag which causes the compiler to emit all deprecation
  warnings, not just 5 per feature.

Dart API

• Add a quietDeps argument to compile(), compileString(),
  compileAsync(), and compileStringAsync() which silences compiler warnings
  from stylesheets loaded through importers, load paths, and package: URLs.

• Add a verbose argument to compile(), compileString(), compileAsync(),
  and compileStringAsync() which causes the compiler to emit all deprecation
  warnings, not just 5 per feature.

v1.33.0

Compare Source

• Deprecate the use of / for division. The new math.div() function should be
  used instead. See this page for details.

• Add a list.slash() function that returns a slash-separated list.

• Potentially breaking bug fix: The heuristics around when potentially
  slash-separated numbers are converted to slash-free numbers—for example, when
  1/2 will be printed as 0.5 rather than 1/2—have been slightly expanded.
  Previously, a number would be made slash-free if it was passed as an argument
  to a user-defined function, but not to a built-in function. Now it will be
  made slash-free in both cases. This is a behavioral change, but it's unlikely
  to affect any real-world stylesheets.

• [:is()][:is()] now behaves identically to :matches().

• Fix a bug where non-integer numbers that were very close to integer
  values would be incorrectly formatted in CSS.

• Fix a bug where very small number and very large negative numbers would be
  incorrectly formatted in CSS.

JS API

• The this context for importers now has a fromImport field, which is true
  if the importer is being invoked from an @import and false otherwise.
  Importers should only use this to determine whether to load import-only
  files.

Dart API

• Add an Importer.fromImport getter, which is true if the current
  Importer.canonicalize() call comes from an @import rule and false
  otherwise. Importers should only use this to determine whether to load
  import-only files.

v1.32.13

Compare Source

• Potentially breaking bug fix: Null values in @use and @forward
  configurations no longer override the !default variable, matching the
  behavior of the equivalent code using @import.

• Use the proper parameter names in error messages about string.slice

---

Configuration

📅 Schedule: 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, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.