FRfridek·Jun 6, 2016
I think the biggest loser in this comparison is Closure Compiler, which is around for years with all those features. It's also still active with development on understanding and transpiling ES6 and even TypeScript from what I've heard [1]. There also made a good move recently, enabling ES6 modules packages instead of its own goog.provide/goog.require.
Yet, the available toolchain for it is years behind others. If you wonder how you should have any live reload development with it, you can either rely on community plugins like grunt-closure-compiler [2] or hope plovr[3] is finally resurrected back to a state where it's usable. This all sounds fine until you think about any unit testing. The only karma runner[4] for closure is simply broken and unmaintained. Even worse, most of npm packages you might want to compile with your code will outpu
Read the rest
t thousands of errors because there is no clear way to whitelist code as "not my code leave it alone".
I can just hope one day Google will publish a yeoman generator with all those things solved and get it back in the game.
[1] https://groups.google.com/forum/#!msg/closure-compiler-discu...
[2] https://github.com/gmarty/grunt-closure-compiler
[3] https://github.com/bolinfest/plovr
[4] https://github.com/karma-runner/karma-closure