This repository has been archived by the owner on Apr 19, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
An in-range update of mini-css-extract-plugin is breaking the build 🚨 #46
Labels
Comments
After pinning to 0.4.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 15 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Version 0.4.1 of mini-css-extract-plugin was just published.
This version is covered by your current version range and after updating it in your project the build failed.
mini-css-extract-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Release Notes
v0.4.10.4.1 (2018-06-29)
Bug Fixes
Commits
The new version differs by 12 commits.
4afcfe2
chore(release): 0.4.1
79373eb
fix: CSS ordering for config with multiple entry points (#130)
1023d22
fix: conflict multiple asset error (#194)
e00bcda
fix: update webpack version (#197)
eff04a8
docs: fix simple example (#189)
0b3a7b2
docs: publicPath documentation (#187)
98b4d0e
docs: do not match .ass (#127)
fd72fd7
docs: fix typo (#169)
7a44b07
refactor: replace literal plugin name in strings with const (#157)
41347f7
docs: add CSS extract based on entry (#121)
2709413
chore(defaults): Applies latest webpack-defaults (#82)
d7d0afc
docs: Add an advanced configuration example (#101)
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: