Update dependency sass from v1.89.2 to v1.98.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
sass	1.89.2 → 1.98.0

---

Release Notes

sass/dart-sass (sass)

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

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.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @sentry/react@7.120.4
npm error Found: react@19.1.1
npm error node_modules/react
npm error   react@"19.1.1" from the root project
npm error   peer react@">=16.8.0" from @emotion/react@11.14.0
npm error   node_modules/@emotion/react
npm error     @emotion/react@"11.14.0" from the root project
npm error     peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.14.1
npm error     node_modules/@emotion/styled
npm error       @emotion/styled@"11.14.1" from the root project
npm error       6 more (@mui/lab, @mui/material, @mui/styled-engine, ...)
npm error     6 more (@mui/lab, @mui/material, @mui/styled-engine, ...)
npm error   25 more (@emotion/styled, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"15.x || 16.x || 17.x || 18.x" from @sentry/react@7.120.4
npm error node_modules/@sentry/react
npm error   @sentry/react@"7.120.4" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"15.x || 16.x || 17.x || 18.x" from @sentry/react@7.120.4
npm error   node_modules/@sentry/react
npm error     @sentry/react@"7.120.4" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-27T10_57_55_214Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-27T10_57_55_214Z-debug-0.log

[atlassian]

🔗 Link your GitHub account to Atlassian

To enable Code Reviewer, please link your GitHub account to your Atlassian account.

Click here to connect your accounts

This is a one-time setup that takes less than a minute.