Update dependency sass-loader to v14
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| sass-loader | ^10.0.5 -> ^14.0.0 |
Release Notes
webpack-contrib/sass-loader (sass-loader)
v14.1.1
v14.1.0
Features
v14.0.0
⚠ BREAKING CHANGES
- removed
fiberssupport - minimum supported Node.js version is
18.12.0(627f55d)
13.3.3 (2023-12-25)
Bug Fixes
13.3.2 (2023-06-09)
Bug Fixes
13.3.1 (2023-05-28)
Bug Fixes
v13.3.3
v13.3.2
v13.3.1
v13.3.0
Features
13.2.2 (2023-03-27)
Bug Fixes
13.2.1 (2023-03-18)
Bug Fixes
- do not crash on a custom scheme in
@import/@usefor the modern API (21966ee)
v13.2.2
v13.2.1
v13.2.0
Features
v13.1.0
Features
13.0.2 (2022-06-27)
Bug Fixes
13.0.1 (2022-06-24)
Bug Fixes
v13.0.2
v13.0.1
v13.0.0
⚠ BREAKING CHANGES
- minimum supported
Node.jsversion is14.15.0(#1048) - emit
@warnat-rules as webpack warnings by default, if you want to revert behavior please use thewarnRuleAsWarningoption (#1054) (58ffb68)
Bug Fixes
- do not crash on importers for modern API (#1052) (095814e)
- do not store original sass error in webpack error(#1053) (06d7533)
v12.6.0
Features
v12.5.0
Features
- added support for
sass-embedded(faster thannode-sass), feel free to feedback - added the
apioption (modernapi is experimental and currently doesn't support built-in webpack resolver) (afbe114)
v12.4.0
Features
v12.3.0
Features
- added the
warnRuleAsWarningoption, allows to emit a warning on the@warnrule (#992) (c652c79) - use webpack logger to log sass messages (only for
dart-sass), configure it using infrastructureLogging (#991) (bb7cef9)
v12.2.0
Features
v12.1.0
Features
- allow
Stringvalue for theimplementationoption (382a3ca)
v12.0.0
⚠ BREAKING CHANGES
- minimum supported
Node.jsversion is12.13.0
Bug Fixes
- crash in custom importers with worker threads (#958) (67aa139)
- resolving
_index.import.scss/index.import.scssin packages (#906) (6641a16)
11.1.1 (2021-05-13)
Bug Fixes
v11.1.1
v11.1.0
Features
11.0.1 (2021-02-08)
Bug Fixes
v11.0.1
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
webpackversion is5
Features
- supported the
resolve.byDependencyoption, you can setup{ resolve: { byDependency: { sass: { mainFiles: ['custom', '...'] } } } }
v10.5.2
10.5.2 (2024-01-04)
Bug Fixes
v10.5.1
10.5.1 (2023-12-19)
Bug Fixes
v10.5.0
Features
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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, check this box
This PR has been generated by Mend Renovate. View repository job log here.