Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Performance Audit 2017: Uglify3 #177

Closed
nicjansma opened this issue Dec 22, 2017 · 2 comments
Closed

Performance Audit 2017: Uglify3 #177

nicjansma opened this issue Dec 22, 2017 · 2 comments
Labels
fixed-akamai Fixed in the Akamai repo performance

Comments

@nicjansma
Copy link

We're currently using Uglify2 for minification.

A quick review of Uglify3 suggests it might shave some bytes:

  • Uglify2: 164,057 bytes
  • Uglify3: 160,490 bytes
@nicjansma
Copy link
Author

This has been fixed in the Akamai fork and will be backported soon.
@nicjansma nicjansma added the fixed-akamai Fixed in the Akamai repo label Dec 31, 2018
@nicjansma
Copy link
Author

We changed from UglifyJS@2 to UglifyJS@3, while also enabling the ie8:true option for compatibility and compress.keep_fnames option to improve Boomerang Error reporting. After all of these changes, Boomerang is 2,074 bytes larger uncompressed, and -706/-723 bytes less gz/br.

Merged in as 65faac0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed-akamai Fixed in the Akamai repo performance
1 participant
@nicjansma