This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of uglify-js.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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.
Hello lovely humans,
uglify-js just published its new version 2.7.4.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of uglify-js. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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:
The new version differs by 367 commits .
557b3e4v2.7.48d74f34Don't filter shebangs when using the 'some' comment filter266ddd9fix uses_arguments handling (broken since 6605d1578351)e51c6baAdd an option for writing inline source map6389e52Remove console.log and add extra test casee05510fAdd an option to wrap IIFEs in parenthesisfc9804bFix (typeof side_effect()) in boolean context4761d07Optimize unmodified variables0111497Make all comment options in cli available in js api7d8dea3Merge pull request #1277 from kzc/fix-string-plus-opt25fc027Account for side effects instring + exproptimization0bd8053implement optimization: (x = 2 * x) ---> (x *= 2)1a78bbcv2.7.38430123Fix negate_iife transform to return a correct tree for nested IIFEs614db97v2.7.2There are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade