3 ms·
You can handle es6+ with the harmony flag but if you're already using Babel is there any reason to use Uglify over Babili? I believe Babili generates minified/
by kjsthree 9y ago
You can handle es6+ with the harmony flag but if you're already using Babel is there any reason to use Uglify over Babili?
I believe Babili generates minified/mangled output directly from the Babel AST which would be way more performant during the dev cycle.
- Androider 9y agoBabili is interesting for sure, but it's at version 0.0.12, clearly marked as beta, requires a bleeding edge Babel, and is 4-6 times slower than Uglify and produces larger output bundle in every single benchmark case with popular libraries on the Babili page itself. So yes, there is clearly still plenty of reasons to use boring old Uglify.
- abritinthebay 9y agoBecause Babili rarely works on Production code (in my experience). I'm sure some people can get it to work but on anything vaguely complex it always errors out for me. It's alpha software for a reason.
- bmpafa 9y agoSimilar experience. Tried it once last week & it was exceptions all the way down. Dunno why Babili is attractive w/ battle-tested uglify still making big moves.
- abritinthebay 9y agoIf you start a project with it it probably works fine (in that you can fix as you go).
- syncopatience 9y agoIf the concern is Uglify slowing down the dev cycle, you could turn it off for development builds.