unstale

npm / sass-loader

sass-loader

What changed in sass-loader 16 to 17, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-17.

3 breaking1 performance1 behavior and defaults3 tooling2 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.1.1 on npm

sass-loader 177 changes

Breaking changes 3

  • Support for the legacy Sass JS API has been removed.

    17.0.0release notes

  • The minimum supported NodeJS version is now 22.11.0.

    17.0.0release notes

  • Support for node-sass has been removed.

    17.0.0release notes

Behavior and default changes 1

  • The api option now defaults to auto, which enables the modern compiler when supported and reuses a long-running compiler across files; otherwise it falls back to the modern API.

    17.0.0release notes

Tooling 2

  • The exports field exposes both ESM and CommonJS builds, allowing ESM consumers to import the loader directly while CommonJS consumers continue to use require.

    17.0.0release notes

  • Types have been added.

    17.0.0release notes

Fixes and other changes 1

  • Removes the BOM from compiled CSS and shifts source maps accordingly, preventing it from breaking a CSS rule when tools move @import at-rules above it.

    17.0.1release notes

sass-loader 163 changes

Performance 1

Tooling 1

  • Updates the peer dependency for @rspack/core v2, allowing sass-loader to declare compatibility with it.

    16.0.7release notes

Fixes and other changes 1

  • Normalizes separators in getPossibleRequests on Windows.

    16.0.8release notes