sass-loader - npm Package Versions

12.4.0 (2021-12-07)

Features

• add support for node-sass 7 (#1002) (be5cbc9)

12.3.0 (2021-10-27)

Features

• added the warnRuleAsWarning option, allows to emit a warning on the @warn rule (#992) (c652c79)
• use webpack logger to log sass messages (only for dart-sass), configure it using infrastructureLogging (#991) (bb7cef9)

12.2.0 (2021-10-12)

Features

• add link field in schema (#976) (1b453fb)

12.1.0 (2021-06-10)

Features

• allow String value for the implementation option (382a3ca)

12.0.0 (2021-06-01)

⚠ BREAKING CHANGES

• minimum supported Node.js version is 12.13.0

Bug Fixes

• crash in custom importers with worker threads (#958) (67aa139)
• resolving _index.import.scss/index.import.scss in packages (#906) (6641a16)

11.1.1 (2021-05-13)

Bug Fixes

• disabled auto importing fiber on node >= 16 due incompatibility problems (#950) (4ca004b)

10.2.0 (2021-05-10)

Features

• support node-sass v6 (dbbbdde)

11.1.0 (2021-05-10)

Features

• support node-sass v6.0.0 (#947) (7869b29)

11.0.1 (2021-02-08)

Bug Fixes

• compatibility with custom importers for node-sass (#927) (af5a072)

11.0.0 (2021-02-05)

Notes

• using ~ is deprecated and can be removed from your code (we recommend it), but we still support it for historical reasons.

Why you can removed it? The loader will first try to resolve @import/@use as relative, if it cannot be resolved, the loader will try to resolve @import/@use inside node_modules. Using ~ means looking for files in node_modules or resolve.alias or resolve.fallback.

⚠ BREAKING CHANGES

• minimum supported webpack version is 5

Features

• supported the resolve.byDependency option, you can setup { resolve: { byDependency: { sass: { mainFiles: ['custom', '...'] } } } }