Update uglify-js to the latest version 🚀 #4849
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Contributor Author
Version 2.8.7 just got published. |
Contributor Author
Version 2.8.8 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits .
See the full diff. |
Contributor Author
Version 2.8.9 just got published. |
Contributor Author
Version 2.8.10 just got published. |
Contributor Author
Version 2.8.11 just got published.Update to this version instead 🚀 Release Notesv2.8.11
CommitsThe new version differs by 5 commits .
See the full diff. |
Contributor Author
Version 2.8.12 just got published.Update to this version instead 🚀 Release Notesv2.8.12
|
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Version 2.8.6 of uglify-js just got published.
The version 2.8.6 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.
Commits
The new version differs by 12 commits .
33b5f31v2.8.635a849dcollapse assignment with adjacent subsequent usage (#1553)b70591bhandle variable declaration within catch blocks (#1546)b33e7f8improveunsafeon undefined (#1548)1f0333estay safe with constants in IE8- (#1547)eb98a7ffix handling of shebang and preamble (#1545)78d1bb9fix a corner case in #1530 (#1552)ea9ab9fresolve issue with outdated version of async (#1549)ce54c9cdisallow collapse_vars constant replacement in for-in statements (#1543)07accd2process code with implicit return statement (#1522)18059cccompress numerical expressions (#1513)b5e0e8cfacilitate fix for #1531 (#1542)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 🌴