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

The devDependency webpack-cli was updated from `3.3.6` to `3.3.7`.

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 passed ([Details](https://travis-ci.org/cssinjs/caniuse-support/builds/573328722?utm_source=github_status&utm_medium=notification)). - ✅ **coverage/coveralls:** First build on greenkeeper/webpack-cli-3.3.7 at 95.652% ([Details](https://coveralls.io/builds/25195023)). - ❌ **continuous-integration/travis-ci/pr:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/cssinjs/caniuse-support/builds/574074228?utm_source=github_status&utm_medium=notification)).

Release Notes for Webpack-CLI v3.3.7

Version 3.3.7 comes with vulnerability patches and a bugfix to using the CLI when there is no configuration file present. A full changelog found here

Commits

The new version differs by 7 commits.

9487ee5 chore: v3.3.7
b20ecd3 Merge pull request #1024 from webpack/fix/no-config-mode
45b9127 chore: resolve differently
43fc033 chore: update lockfile & pass nil
97d5c75 chore: lock deps
635bfa3 chore: lock deps
fb31cc4 fix: resolve opts when no-config

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:

cssinjs / caniuse-support