An in-range update of uglify-js is breaking the build π¨
greenkeeper opened this issue Β· 2 comments
The devDependency uglify-js was updated from 3.5.2
to 3.5.3
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
uglify-js 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).
Release Notes for v3.5.3
Commits
The new version differs by 3 commits.
fa43768
v3.5.3
a74e600
mangle shadowed lambda under
ie8
correctly (#3356)4b21526
Fix test expectation (#3357)
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 π΄
After pinning to 3.5.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependency
uglify-js was updated from3.5.3
to3.5.4
.
Your tests are passing again with this update. Explicitly upgrade to this version π
Release Notes for v3.5.4