News for hackers. Stuff that matters.
Re:Huge no. of files for Angular 2 by Akkuma on Tuesday August 02, 2016 @09:28AM (#12209748)
Buble's purpose is that it is supposed to be significantly faster to compile from ES6 to ES5 with minimal configuration, since it actually does things out of the box.
Re:Huge no. of files for Angular 2 by Klathmon on Tuesday August 02, 2016 @09:39AM (#12209821)
But that has nothing to do with it's size. If Buble was 10% larger than Babel it would still solve it's purpose.
Re:Huge no. of files for Angular 2 by Touche on Tuesday August 02, 2016 @10:25AM (#12210156)
That's right, Buble's secret sauce to being fast is that is skips the code generation step, not because of the number of dependencies.

Although there definitely is a performance cost to Babel's large dep tree as each of these modules have to be found by Node (which is inefficient). If you use Babel with npm2 it is super slow, because npm2's folder structure causes more lookups.

Re:Huge no. of files for Angular 2 by sotojuan on Tuesday August 02, 2016 @10:42AM (#12210283)
We ship Babel built in with the AVA[1] test runner and I can confirm `babel-require` is our bottleneck.

[1] https://github.com/avajs/ava

Re:Huge no. of files for Angular 2 by Touche on Tuesday August 02, 2016 @02:37PM (#12212149)
Yeah, I think that was a bit of a mistake by you guys. AVA's entire point is to be fast but it has the perception of being slow because you've made transpiling a core feature. I would drop that and let people do their own transpiling.
Re:Huge no. of files for Angular 2 by sotojuan on Tuesday August 02, 2016 @08:29PM (#12214558)
Aside from the concurrent testing, Babel with async functions built-ins is our second biggest "bullet point", so even if you were right it's too late. AVA is opinionated and I think the benefits (from what people have told us) gained from using the latest syntax with no Babel config are worth the Babel bottleneck—which isn't that bad.