This version is covered by your current version range and after updating it in your project the build went from success to failure.
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 :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
uglify-js just published its new version 2.8.14.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
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 :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
The new version differs by 142 commits .
30a7504
v2.8.14
a3cc3a9
make
expect_stdout
work on Node.js 0.12 (#1623)96f8bef
fix commit 88fb83a (#1622)
cd58635
fix AST_Binary.lift_sequences() (#1621)
274331d
transform String.charAt() to index access (#1620)
0489d6d
handle runtime errors in
expect_stdout
(#1618)fb09283
fix top-level directives in compress tests (#1615)
b7c112e
Add
--in-source-map inline
documentation (#1611)b2b8a0d
v2.8.13
ac40301
fix chained evaluation (#1610)
3563d8c
extend
test/run-tests.js
to optionally execute uglified output (#1604)5ae04b3
make
collapse_vars
consistent withtoplevel
(#1608)a80b228
fix
hoist_vars
onreduce_vars
(#1607)cf4bf4c
fix stack issues with
AST_Node.evaluate()
(#1603)8223b2e
fix
AST_Node.optimize()
(#1602)There are 142 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.