Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump mini-css-extract-plugin from 1.6.2 to 2.0.0 #1332

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 1, 2021

Bumps mini-css-extract-plugin from 1.6.2 to 2.0.0.

Release notes

Sourced from mini-css-extract-plugin's releases.

v2.0.0

2.0.0 (2021-06-30)

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 the outputPath option for file-loader and etc. Now you don't need it anymore. Webpack v5 uses publicPath: "auto" by default, which means to always generate relative URLs, and now mini-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 and url-loader are outdated, please migrate on Asset Modules.

⚠ 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, just remove it
  • the publicPath 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 have publicPath: "/my/public/path" replace it with publicPath: "/my/public/path/"

Bug Fixes

  • generating correct relative url() for assets inside CSS files when you use publicPath: "auto" (default value)
Changelog

Sourced from mini-css-extract-plugin's changelog.

2.0.0 (2021-06-30)

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 the outputPath option for file-loader and etc. Now you don't need it anymore. Webpack v5 uses publicPath: "auto" by default, which means to always generate relative URLs, and now mini-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 and url-loader are outdated, please migrate on Asset Modules.

⚠ 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, just remove it
  • the publicPath 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 have publicPath: "/my/public/path" replace it with publicPath: "/my/public/path/"

Bug Fixes

  • generating correct relative url() for assets inside CSS files when you use publicPath: "auto" (default value)
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [mini-css-extract-plugin](https://github.com/webpack-contrib/mini-css-extract-plugin) from 1.6.2 to 2.0.0.
- [Release notes](https://github.com/webpack-contrib/mini-css-extract-plugin/releases)
- [Changelog](https://github.com/webpack-contrib/mini-css-extract-plugin/blob/master/CHANGELOG.md)
- [Commits](webpack-contrib/mini-css-extract-plugin@v1.6.2...v2.0.0)

---
updated-dependencies:
- dependency-name: mini-css-extract-plugin
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added automerge Will be auto merged if tests pass dependencies Pull requests that update a dependency file npm labels Jul 1, 2021
@kodiakhq kodiakhq bot merged commit 99602d5 into master Jul 1, 2021
@kodiakhq kodiakhq bot deleted the dependabot/npm_and_yarn/mini-css-extract-plugin-2.0.0 branch July 1, 2021 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Will be auto merged if tests pass dependencies Pull requests that update a dependency file npm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants