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

[greenkeeper[bot]]

Version 3.0.2 of extract-text-webpack-plugin was just published.

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

This version is covered by your current version range and after updating it in your project the build failed.

extract-text-webpack-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

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/DBCDK/tanterne/builds/292769385?utm_source=github_status&utm_medium=notification)

---

Release Notes

Release v3.0.2

3.0.2 (2017-10-25)

Bug Fixes

• refer to the entrypoint instead of the first module (module.identifier) (#601) (d5a1de2)

Commits

The new version differs by 3 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)

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 3.0.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[fvsdbc]

Fixed