Upgrade style-loader: 1.3.0 → 3.3.0 (major)

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ style-loader (1.3.0 → 3.3.0) · Repo · Changelog

Release Notes

3.3.0

3.3.0 (2021-09-21)

Features

• added support for supports(), layer() and media from @import at-rules (b9a600c)
• allow to pass options to insert function through style.use() (#535) (f8ef63b)

3.2.1

3.2.1 (2021-07-20)

Bug Fixes

• added the styletagtransform option when it is a module to addBuildDependency (#528) (270513f)

3.2.0

3.2.0 (2021-07-20)

Features

• add link field in schema (#525) (7ed3456)

Bug Fixes

• added the insert option when it is a module to addBuildDependency (#527) (3963c0b)

3.1.0

3.1.0 (2021-07-12)

Features

• allow to specify the insert option from file, we strongly recommend do it, using the insert option from file will reduce your bundle size, example (#521) (56fc8f0)
• allow to specify the styleTagTransform option from file, we strongly recommend do it, using the styleTagTransform option from file will reduce your bundle size, example

Bug Fixes

• reduce runtime (#519) (8a26186)
• reduce runtime when you use custom options (#520) (21c80c8)

3.0.0

3.0.0 (2021-06-24)

⚠ BREAKING CHANGES

• minimum supported Node.js version is 12.13.0
• minimum supported webpack version is 5.0.0
• the modules.namedExport option was removed, you don't need it anymore, because we respect the modules.namedExport option from css-loader (we just reexport all from css-loader), just remove it
• the styleTag value of the injectType (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 setting autoStyleTag value for the injectType option (do the same for lazyStyleTag, i.e. change it to lazyAutoStyleTag)

Features

• added autoStyleTag and lazyAutoStyleTag values for the injectType option for compatibility of work modern and IE8-IE9 browsers
• added styleTagTransform option for custom processing style tags (useful if you need ponyfill CSS custom properties for IE8-IE10)
• reduce size of generated code
• reduce deps

2.0.0

⚠ BREAKING CHANGES

• minimum supported Node.js version is 10.13.0
• the esModule option is true by default, you need to change const locals = require('./styles.css')/require('./styles.css') on import locals from './styles.css'/import './styles.css'' (#489) (727a24d)
• removed support for loaders returning String instead of Array (#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.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 40 commits:

• chore(release): 3.3.0
• test: update (#542)
• refactor: code (#541)
• feat: added support for `@supports`, `@layer` and `@media` from `@import` at-rules
• chore(deps): update (#539)
• refactor: code
• chore(deps): update
• feat: allow to pass options to `insert` function through `style.use()` (#535)
• docs: update bug report template (#534)
• docs: update README (#533)
• ci: update `codecov-action` (#532)
• ci: update commitlint action to v4 (#531)
• ci: setup npm cache (#529)
• chore(release): 3.2.1
• fix: added the `styletagtransform` option when it is a module to `addBuildDependency` (#528)
• chore(release): 3.2.0
• fix: added the `insert` option when it is a module to `addBuildDependency` (#527)
• ci: use `actions/setup-node@v2` (#524)
• feat: add link field in schema (#525)
• chore(release): 3.1.0
• feat: styleTagTransform option processed absolute path (#522)
• feat: allow to specify the `insert` option from file, we strongly recommend do it when you specify the custom `insert` option to reduce bundle size (#521)
• fix: reduce runtime when you use custom options (#520)
• fix: reduce runtime (#519)
• chore(release): 3.0.0
• refactor: next (#501)
• ci: update nodejs.yml (#515)
• chore: update deps (#516)
• chore: fix typo (#512)
• chore: update deps and fix audit (#514)
• docs: recommend (#507)
• docs: fix link on webpack-dll-plugins (#500)
• chore(deps): update (#499)
• Merge pull request #492 from webpack-contrib/ci-updated
• ci: updated webpack versions
• chore(release): 2.0.0
• refactor: removed support for loaders returning `String` instead of `Array` (#491)
• test: refactor (#490)
• feat: enabled esModule by default (#489)
• chore: updated deps (#488)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)