An in-range update of terser-webpack-plugin is breaking the build 🚨
Closed this issue · 1 comments
greenkeeper commented
The devDependency terser-webpack-plugin was updated from 2.2.1 to 2.2.2.
This version is covered by your current version range and after updating it in your project the build failed.
terser-webpack-plugin 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).
- ✅ license/cla: All CLA requirements met.
- ❌ continuous-integration/travis-ci/pr: The Travis CI build could not complete due to an error (Details).
- ❌ codecov/project: CI failed. (Details).
- ❌ codecov/patch: CI failed. (Details).
- ❌ Travis CI - Pull Request:
The build errored. This is a change from the previous build, which passed.
- ✅ build (13.x): null
- ✅ build (12.x): null
- ✅ build (11.x): null
- ✅ build (10.x): null
- ✅ Travis CI - Branch:
The build passed.
The build
The buildFAQ 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 commented
After pinning to 2.2.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.