An in-range update of uglify-js is breaking the build π¨
greenkeeper opened this issue Β· comments
Version 3.0.23 of uglify-js just got published.
Branch | Build failing π¨ |
---|---|
Dependency | uglify-js |
Current Version | 3.0.22 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As uglify-js is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
Release Notes
v3.0.23
Commits
The new version differs by 3 commits.
2dde416
v3.0.23
8b69a3d
drop argument value after
collapse_vars
(#2190)d40950b
improve
inline
efficiency (#2188)
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
After pinning to 3.0.22 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 3.0.24 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version π
Release Notes
v3.0.24
Commits
The new version differs by 11 commits.
bd7be07
v3.0.24
71ee91e
handle duplicate argument names in
collapse_vars
(#2215)4f70d2e
inlining of static methods & constants (#2211)
4b6ca5e
inline property access of object literal (#2209)
9306da3
suppress
collapse_vars
ofthis
as call argument (#2204)1ac25fc
improve
compress
granularity throughtypeofs
(#2201)5f046c7
minor clean-ups to
evaluate
(#2197)af0262b
improve parenthesis emission (#2196)
6b3aeff
clean up
TreeWalker.pop()
(#2195)20e4f82
refactor
throw
usage withincompress
(#2193)f3a487a
document fast mangle-only minify mode (#2194)
See the full diff