chore(deps): update dependency less-loader to v11 - autoclosed #140
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^6
->^11.1.4
Release Notes
webpack-contrib/less-loader (less-loader)
v11.1.4
Compare Source
v11.1.3
Compare Source
v11.1.2
Compare Source
v11.1.1
Compare Source
v11.1.0
Compare Source
Features
conditionNames
(#488) (43cd20c)v11.0.0
Compare Source
⚠ BREAKING CHANGES
Node.js
version is14.15.0
v10.2.0
Compare Source
Features
v10.1.0
Compare Source
Features
link
field in schema (#429) (8580731)Bug Fixes
addDependency
on absolute paths (fa11ce7)10.0.1 (2021-07-02)
Bug Fixes
v10.0.1
Compare Source
v10.0.0
Compare Source
⚠ BREAKING CHANGES
less.webpackLoaderContext
was removed, please usepluginManager.webpackLoaderContext
Bug Fixes
v9.1.0
Compare Source
Features
String
value for theimplementation
option (465ffc4)v9.0.0
Compare Source
⚠ BREAKING CHANGES
Node.js
version is12.13.0
8.1.1 (2021-04-15)
Bug Fixes
v8.1.1
Compare Source
v8.1.0
Compare Source
Features
pluginManager.webpackLoaderContext
property forless
plugin developers, deprecated theless.webpackLoaderContext
property, it fixed memory leak, please read this (#412) (e576240)v8.0.0
Compare Source
Notes
~
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
as relative, if it cannot be resolved, the loader will try to resolve@import
insidenode_modules
.⚠ BREAKING CHANGES
webpack
version is5
Features
resolve.byDependency
option, you can setup{ resolve: { byDependency: { less: { mainFiles: ['custom', '...'] } } } }
v7.3.0
Compare Source
Features
implementation
option (84d957c)7.2.1 (2020-12-28)
Bug Fixes
v7.2.1
Compare Source
v7.2.0
Compare Source
Features
v7.1.0
Compare Source
Features
additionalData
to be async (#391) (62c6934)7.0.2 (2020-10-09)
Chore
schema-utils
7.0.1 (2020-09-03)
Bug Fixes
sources
in source maps (877d99a)v7.0.2
Compare Source
v7.0.1
Compare Source
v7.0.0
Compare Source
⚠ BREAKING CHANGES
less
topeerDependencies
, theimplementation
option was removedprependData
andappendData
option were removed in favor theadditionaldata
optionFeatures
webpackImporter
option (#377) (12dca5b)additionaldata
option (#374) (2785803)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.
This PR has been generated by Mend Renovate. View repository job log here.