Update uglify-js to the latest version 馃殌 #30
Closed
Conversation
This file contains 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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 3.0.1 just got published.Update to this version instead 馃殌 Release Notesv3.0.1聽 |
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 3.0.0 of uglify-js just got published.
The version 3.0.0 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.
Release Notes
v3.0.0聽
Commits
The new version differs by 34 commits0.
7313465v3.0.02c7ee95fixunsafeonevaluateofreduce_vars(#1870)ecf3563killopera(#1869)dee5a27enhancecollapse_vars(#1862)5a25d24rename variables for better readability (#1863)bffdc8dupdatetest/benchmark.jsresources (#1864)69b5663restore report of supported options (#1861)ea92897improve literal return optimization (#1860)2cb55b2enforcetoplevelon other compress options (#1855)bbb5f2aUpdate ISSUE_TEMPLATE.md (#1846)76d19b6fix fuzzer onthis(#1842)9e62628fixunusedon for-in statements (#1843)9bf72cfimprove parser under "use strict" (#1836)64d7443update README for 3.x (#1840)45ce369fixAST_For.initpatch-up indrop_unused()(#1839)There are 34 commits in total.
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 馃尨