An in-range update of extract-text-webpack-plugin is breaking the build 🚨

[greenkeeper]

Version 2.1.1 of extract-text-webpack-plugin just got published.

Branch	Build failing 🚨
Dependency	extract-text-webpack-plugin
Current Version	2.1.0
Type	devDependency

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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

Release v2.1.1

2.1.1 (2017-06-08)

Bug Fixes

• add a not null check for the content property before throwing error (#404) (58dd5d3)
• loader: rm unnecessary this.cacheable (caching) (#530) (c3cb091)
• don't extract from common async chunks (#508) (e595417)
• validation schema (schema-utils) (#527) (dfeb347)

Commits

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

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

Version 2.1.2 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

v2.1.2

Bug Fixes

• index: resolve schemas relative to __dirname (#536)(87668210)

Commits

The new version differs by 2 commits.

• e81b883 chore(release): 2.1.2
• 8766821 fix(index): resolve schemas relative to __dirname (#536)

See the full diff