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

[greenkeeper]

The devDependency webpack-cli was updated from 3.3.8 to 3.3.9.

🚨 View failing branch.

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

webpack-cli 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 3 commits.

• 48c03ab chore: v3.3.9
• a1341bd Merge pull request #1078 from lneveu/fix/process-exit-hang
• ee001bd fix: use process.exitCode instead of process.exit in compilerCallback

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

[greenkeeper]

• The devDependency webpack-cli was updated from 3.3.9 to 3.3.10.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for Webpack CLI v3.3.10

Version 3.3.10 comes with a new flag no-cache, version patches to security and removal of out-of-sync mono-repo tests. The change is considered a patch, since no functionality is changed.

Full changelog found here

Commits

The new version differs by 4 commits.

• f9f0860 chore: v3.3.10
• 08a7650 chore: remove un-synced tests
• 1208aa6 feat: add new flag and patch sec dep (#1102)
• 6ad6099 chore: sec patch

See the full diff