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

[greenkeeper[bot]]

The devDependency webpack was updated from 4.41.6 to 4.42.0.

🚨 View failing branch.

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](https://travis-ci.org/Dreamseer/elements/builds/657205225?utm_source=github_status&utm_medium=notification)).

---

Release Notes for v4.42.0

Bugfixes

• Disable constant replacements in "use asm" scope
• Update schema to disallow functions for output.hotUpdateChunkFilename as this doesn't work
• Hoist exports in concatenated module to handle circular references with non-concatenated modules correctly
• Flag all modules as used in DLLs to fix missing exports

Commits

The new version differs by 11 commits.

• 29d851b 4.42.0
• 07a4b28 Merge pull request #10478 from webpack/bugfix/all-modules-dll
• c1aa9d4 flag all modules as used for Dll
• d147689 Merge pull request #10431 from webpack/bugfix/concat-circular-4
• d76761d hoist exports to the top of a concatenated module
• 534d78f Merge pull request #10393 from webpack/schema/disallow-function-hotchunkfilename
• d46ddc2 disallow function for output.hotUpdateChunkFilename
• 95409bd Merge pull request #10294 from ngg/asmjs-4
• 7a30012 spacing
• 284e97f add detectStrictMode method for backward-compat
• a7a07bc do not evaluate constants in asm.js, fix IIFE mode detection

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 4.41.6 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.