v11.0.0

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', '...'] } } } }

v10.1.1

10.1.1 (2021-01-11)

Bug Fixes

• problem with resolving and the includePaths option (#913) (cadc75e)

v10.1.0

10.1.0 (2020-11-11)

Features

• allow the additionalData to be async (#902) (9d925ff)

v10.0.5

10.0.5 (2020-11-02)

Bug Fixes

• support node-sass v5.0.0 (#899) (c3e279f)

v10.0.4

10.0.4 (2020-10-22)

Bug Fixes

• compatibility with the filesystem cache (#896) (e31f9b6)

v10.0.3

10.0.3 (2020-10-09)

Chore

• update schema-utils

v10.0.2

10.0.2 (2020-09-03)

Bug Fixes

• source maps generation (#886) (8327d55)

v10.0.1

10.0.1 (2020-08-25)

Chore

• update deps

v10.0.0-rc.0

10.0.0-rc.0 (2020-08-24)

⚠ BREAKING CHANGES

• loader generates absolute sources in source maps, also avoids modifying sass source maps if the sourceMap option is false

v10.0.0

10.0.0 (2020-08-24)

Bug Fixes

• handle absolute windows path in source maps

See notes for https://github.com/webpack-contrib/sass-loader/releases/tag/v10.0.0-rc.0 release