ion-app-web
ion-app-web copied to clipboard
Update dependency style-loader to v3
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| style-loader | 1.3.0 -> 3.3.1 |
Release Notes
webpack-contrib/style-loader
v3.3.1
v3.3.0
Features
- added support for
supports(),layer()andmediafrom@importat-rules (b9a600c) - allow to pass options to
insertfunction throughstyle.use()(#535) (f8ef63b)
3.2.1 (2021-07-20)
Bug Fixes
v3.2.1
v3.2.0
Features
Bug Fixes
v3.1.0
Features
- allow to specify the
insertoption from file, we strongly recommend do it, using theinsertoption from file will reduce your bundle size, example (#521) (56fc8f0) - allow to specify the
styleTagTransformoption from file, we strongly recommend do it, using thestyleTagTransformoption from file will reduce your bundle size, example
Bug Fixes
v3.0.0
⚠ BREAKING CHANGES
- minimum supported
Node.jsversion is12.13.0 - minimum supported
webpackversion is5.0.0 - the
modules.namedExportoption was removed, you don't need it anymore, because we respect themodules.namedExportoption fromcss-loader(we just reexport all fromcss-loader), just remove it - the
styleTagvalue 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 settingautoStyleTagvalue for theinjectTypeoption (do the same forlazyStyleTag, i.e. change it tolazyAutoStyleTag)
Features
- added
autoStyleTagandlazyAutoStyleTagvalues for theinjectTypeoption for compatibility of work modern and IE8-IE9 browsers - added
styleTagTransformoption for custom processing style tags (useful if you need ponyfill CSS custom properties for IE8-IE10) - reduce size of generated code
- reduce deps
v2.0.0
⚠ BREAKING CHANGES
- minimum supported
Node.jsversion is10.13.0 - the
esModuleoption istrueby default, you need to changeconst locals = require('./styles.css')/require('./styles.css')onimport locals from './styles.css'/import './styles.css''(#489) (727a24d) - removed support for loaders returning
Stringinstead ofArray(#491) (7a0ce4c)
⚠ NOTICE
To avoid problems between style-loader and mini-css-extract-plugin because of changing the esModule option to true by default we strongly recommend upgrading mini-css-extract-plugin to 1.0.0 version.
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, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm WARN using --force Recommended protections disabled.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/webpack
npm ERR! dev webpack@"4.46.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^5.0.0" from [email protected]
npm ERR! node_modules/style-loader
npm ERR! dev style-loader@"3.3.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2021-12-08T09_13_14_463Z-debug-0.log