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.0.1
to 2.1.0
.
π¨ View failing branch.
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 could not complete due to an error (Details).
Commits
The new version differs by 9 commits.
d5df728
chore(release): 2.1.0
9bbe824
refactor: code (#158)
aba8ba7
fix: correct interpretation url for extracted comment file (#157)
2b4d2a4
feat: emit warning when comment file conlict with an existing asset (#156)
efbd383
docs: add missing breaking change for 2.0.0 (#155)
5fe3337
feat: improve naming of extracted file with comments (#154)
cea7243
Chore deps update (#153)
5821456
docs: clarify default value for sourceMap option (#151)
cf91c43
docs: update readme to reflect new default options (#147)
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 commented
After pinning to 2.0.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.