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.0.0
->7.0.1
1.6.0
->2.1.0
2.0.0
->3.0.0
Release Notes
typicode/husky
v7.0.1
Compare Source
v7.0.0
Compare Source
.husky/
directory structure..husky/.gitignore
is now unnecessary and can be removed.husky-init
CLIhusky-4-to-7
CLIPlease help me develop and release OSS projects ❤️ on GitHub Sponsors or Open Collective. Thank you for your support!
webpack-contrib/mini-css-extract-plugin
v2.1.0
Compare Source
Features
pathinfo
option (#783) (a37713f)v2.0.0
Compare Source
NOTES
In the current release we have fixed many problems with
publicPath
, previously to generate relative URLs inside CSS files developers use different hacks:publicPath: ''
,publicPath: '../'
, using relative../../
in theoutputPath
option forfile-loader
and etc. Now you don't need it anymore. Webpack v5 usespublicPath: "auto"
by default, which means to always generate relative URLs, and nowmini-css-extract-plugin
does the same.We strongly recommend use
auto
value by default (except when using CDN).We also want to show you that the
file-loader
andurl-loader
are outdated, please migrate on Asset Modules.⚠ BREAKING CHANGES
Node.js
version is12.13.0
webpack
version is5.0.0
modules.namedExport
option was removed, you don't need it anymore, because we respect themodules.namedExport
option fromcss-loader
, just remove itpublicPath
option no longer automatically adds/
(trailing slash), you need to specify, you need to specify it yourself if it is absent, i.e. if you havepublicPath: "/my/public/path"
replace it withpublicPath: "/my/public/path/"
Bug Fixes
url()
for assets inside CSS files when you usepublicPath: "auto"
(default value)1.6.2 (2021-06-28)
Bug Fixes
1.6.1 (2021-06-25)
Bug Fixes
v1.6.2
Compare Source
v1.6.1
Compare Source
webpack-contrib/style-loader
v3.0.0
Compare Source
⚠ BREAKING CHANGES
Node.js
version is12.13.0
webpack
version is5.0.0
modules.namedExport
option was removed, you don't need it anymore, because we respect themodules.namedExport
option fromcss-loader
(we just reexport all fromcss-loader
), just remove itstyleTag
value of theinjectType
(default value) option earlier uses singleton style tag by default for IE8-IE9 due limitations (more information), in this release we have disabled this behavior, because these versions of IE are outdated, if you don't support these browsers this change does not affect you, if you require to support IE8-IE9, you can return old behaviour by settingautoStyleTag
value for theinjectType
option (do the same forlazyStyleTag
, i.e. change it tolazyAutoStyleTag
)Features
autoStyleTag
andlazyAutoStyleTag
values for theinjectType
option for compatibility of work modern and IE8-IE9 browsersstyleTagTransform
option for custom processing style tags (useful if you need ponyfill CSS custom properties for IE8-IE10)Configuration
📅 Schedule: "before 3am on Monday" (UTC).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by WhiteSource Renovate. View repository job log here.