Closed greenkeeper[bot] closed 7 years ago
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 13 commits.
0271b39
chore(release): 2.1.1
e595417
fix: don't extract from common async chunks (#508)
a8ae003
chore(package): fix broken links && update devDependencies (#531)
c3cb091
fix(loader): rm unnecessary this.cacheable
(caching) (#530)
eaa5236
docs: rm RELEASE.md
(#532)
671e35e
chore(package): update webpack-sources
v0.1.0...1.0.1 (#526)
dfeb347
fix: validation schema (schema-utils
) (#527)
d0e88d0
docs(README): add lead-in description (#517)
58dd5d3
fix: add a not null check for the content property before throwing error (#404)
6c50d8e
Update README.md (#469)
c63dc04
docs(README): clarify to set allChunks option when using CommonsChunkPlugin (#476)
c40dc64
chore(package): reduce package size (#482)
a284f3a
docs(README): fix options table formatting (#478)
See the full diff
Your tests are still failing with this version. Compare the changes 🚨
__dirname
(#536) (8766821) (@MirrorBytes)Your tests are passing again with this version. Explicitly upgrade to this version 🚀
The new version differs by 11 commits.
cc3ba94
chore(release): 3.0.2
d5a1de2
fix: refer to the entrypoint
instead of the first module
(module.identifier
) (#601)
5286ab2
build(defaults): update to v1.6.0 (#652)
4cfde50
chore(release): 3.0.1
8de6558
fix: get real path from __filename
instead of __dirname
(NS
)
510704f
fix(index): stricter check for shouldExtract !== wasExtracted
(#605)
6a660f3
docs(README): update install instructions (#570)
083a6c8
docs(README): add custom [contenthash]
formats (#566)
d7a75fc
chore(release): 3.0.0
7ae32d9
refactor: Apply webpack-defaults & webpack 3.x support (#540)
dd43832
fix: add missing options.ignoreOrder
details in Error message (#539)
See the full diff
Version 2.1.0 of extract-text-webpack-plugin just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As extract-text-webpack-plugin is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **dependency-ci** Failed dependency checks [Details](https://dependencyci.com/builds/162554)Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: