Skip to content
This repository was archived by the owner on Aug 7, 2021. It is now read-only.

Switch from UglifyJs to Terser #863

Closed
DimitarTachev opened this issue Apr 15, 2019 · 1 comment
Closed

Switch from UglifyJs to Terser #863

DimitarTachev opened this issue Apr 15, 2019 · 1 comment
Assignees

Comments

@DimitarTachev
Copy link
Contributor

Describe the solution you'd like
Terser is a fork of Uglify that retains the API and CLI compatibility. It shouldn’t really change the results, but it has more maintainers and fixes for a few long-standing issues with UglifyJS. Also, it's already used in Angular, Vue and React and we will unify the minification process in our Web + Mobile Code Sharing stories.

Additional context
webpack-contrib/terser-webpack-plugin#15
webpack/webpack#7923

@DimitarTachev
Copy link
Contributor Author

Acceptance Criteria:

[ ] The uglified app size with Terser should be less or equel compared to the one with UglifyJs.
[ ] The uglified app build time with Terser should be less or equel compared to the one with UglifyJs.
[ ] The uglified app error stack traces should contain the proper line numbers based on the source maps (hidden or not).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants