Hello lovely humans,

uglify-js just published its new version 2.8.5.

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 💪

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 ✨

You rock!

🌴

The new version differs by 179 commits .

• e5cb927 v2.8.5
• 17b8135 fix chained assignment with unused (#1540)
• 4d63d4f collapse_vars should not replace constant in for-in init section (#1538)
• 70d72ad properly cover all cases of for-in loop variables (#1536)
• fe9227a fix reference marking in for-in loops (#1535)
• b49e142 disable do{...}while(false) optimisation (#1534)
• ee3b39b optimize trivial IIFEs returning constants (#1530)
• 9699ffb trim unused invocation parameters (#1526)
• fdc9b94 minor improvement to string optimisation (#1514)
• 40ceddb v2.8.4
• 7aa6911 fix corner cases in reduce_vars (#1524)
• bff7ad6 v2.8.3
• c2334ba fix crash on missing props to string_template() (#1523)
• fb2b6c7 v2.8.2
• f5cbe19 invert reduce_vars tracking flag (#1519)

There are 179 commits in total. See the full diff.