The premise is attractive, but the challenge will be keeping up with a rapidly-changing ecosystem. The advantage of letting Webpack and Babel be separate, havin

The premise is attractive, but the challenge will be keeping up with a rapidly-changing ecosystem. The advantage of letting Webpack and Babel be separate, having both as singular community focal-points for their respective tasks, and having both be extensible via plugins (the TypeScript team can work independently from the Babel team, for example), is that the leg-work of adding new JS features, parsing new syntaxes, keeping up with the spec, etc. can be distributed in the most efficient way possible. A single team trying to do everything in-house, duplicating the work of all of the above communities, will have a very hard time keeping up. But I wish them luck.