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

[greenkeeper]

The devDependency webpack-command was updated from 0.4.1 to 0.4.2.

🚨 View failing branch.

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

webpack-command 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.

• feda7e0 test: update snapshots
• 1c5e1e6 chore: update package lock
• 0db82b3 chore: fix ci config
• 2b6361a chore(release): 0.4.2
• 245bee5 chore: prep for fork release
• 1e8dfdd deprecated? nawwww
• be83d80 Update README.md

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