-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uglify-es unmaintained #721
Comments
I'd recommend spending initial time (1-2 hours)? investigating a proactive switch--if the API is compatible and transition is easy, then great. If we run into severe issues or compatibility issues we can re-evaluate. |
From the documentation:
So it seems like it should be fairly straightforward. |
@zepumph volunteered to investigate this |
Was easy to do while investigating uglification times. Handled on the modules branch, closing. |
The release of uglify-es (the support for ES6) has been unmaintained for a number of months, and development looks like it has switched to https://github.com/terser-js/terser (see mishoo/UglifyJS#3156 (comment)).
Is it worth proactively switching, or waiting until we need some sort of upgrade?
The text was updated successfully, but these errors were encountered: