Dropped uglifier support #166
Merged
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
|
Good work! We'll land this when we cut a new major dropping Node 6 support. |
|
I think we should land this, drop Node 6, and cut a new major. |
|
I can rebase it on top of master upd: done |
|
I've rebased this to a next branch, so we can land when we cut v2. |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
As far as I understand the issue #97, uglify-es was added to improve throughput in Node.js 6 which is EOL nowadays and I guess it can be safety dropped now.
One more point to drop support is that uglify-es is no longer maintained
Closes #97