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.

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

Try https://github.com/babel/babili instead of uglify #153

Closed
eduardolundgren opened this issue Aug 26, 2016 · 2 comments

Comments

@eduardolundgren
Copy link
Contributor

Babili seems to be trying to solve the problem in a closer way to Google Closure Compiler. Worth giving a try to see how this affects our minified codebase.

@mairatma
Copy link
Contributor

Will do

@mairatma
Copy link
Contributor

It seems like the main advantage of babili is when it's used to uglify code using ES2015, but that won't be transpiled to ES5 (they say that in their README). For ES5 their own benchmarks show that babili loses to uglify (the one we're using). I checked on our code anyway just to be sure, and uglify really did a lot better. Maybe once all the browsers we target support ES2015 it'd be better to use it instead.

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

No branches or pull requests

2 participants