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

[greenkeeper]

The devDependency webpack-merge was updated from 4.2.1 to 4.2.2.

🚨 View failing branch.

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

webpack-merge 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).

---

Commits

The new version differs by 7 commits.

• d35e176 4.2.2
• a53214d Update lib
• ec35567 chore: Update changelog
• a56d5cb chore(merge): Update lodash to avoid npm audit warning
• ef4c067 docs(merge): Improve merge.unique docs
• ad2f92a docs(readme): Add a note about precedence
• c3a5156 chore: Add @desfero to contributors

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