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

[greenkeeper]

Version 4.12.2 of webpack was just published.

Branch	Build failing 🚨
Dependency	[webpack](https://github.com/webpack/webpack)
Current Version	4.12.1
Type	devDependency

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

webpack 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 could not complete due to an error Details
• ✅ coverage/coveralls First build on greenkeeper/webpack-4.12.2 at 100.0% Details

---

Release Notes

v4.12.2

Bugfixes

• fix crash when using invalid JSON with HMR
• fix missing modules when a side-effect-free package is root of module concatenation
• update chunkhash when entry-chunks list or prefetched chunks change

Commits

The new version differs by 19 commits.

• c384c3f 4.12.2
• 9dacf86 Merge pull request #7601 from webpack/bugfix/hash-entry-chunks
• e38e076 fixes #7577
• aab3554 Merge pull request #7574 from byzyk/types/ignore-plugin
• 258d9b6 Merge pull request #7600 from webpack/bugfix/missing-module
• 8cb9241 Merge pull request #7595 from webpack/remove_circle
• 504e1d8 Merge pull request #7590 from webpack/bugfix/json-stringify
• ab7ecb3 fixes #7499
• 3e3827e Remove CircleCI
• 35a7f65 add test case
• 4d57d78 generate error code when json wasn't parsed
• a5e55de skip harmony accept dependency in non-harmony modules
• 720f3b2 make hot cases better
• 94c7273 Merge branch 'master' of https://github.com/kamranahmedse/webpack into bugfix/json-stringify
• a96ac96 add type for resource and context

There are 19 commits in total.

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 🌴

[greenkeeper]

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