> Not to take away from your excitement or the validity of the change, but non frontenders find webpack rather bloated. To be fair, I’ve met more than one front-end developer with the same perception.

Regardless it still seems to be the build system most major platforms and large orgs are choosing to integrate with (for better or worse). Which comes with its own benefits.

It might not be the best build system for a raw new js project but in terms of broad support, stability, adoption rates, 'no one ever got fired for choosing IBM', etc it seems to be the system of choice.

There's no panacea when it comes to front-end build tools, but the webpack 4 release vastly improved configuration and docs, which was a big reason for us to make the jump. We've maintained the old brunch workflow for non-js pros, where you place js in assets/js and css in assets/css and things Just Work™, so folks fond of the old brunch way can continue to handle assets exactly as before, but webpack will be used underneath. I also like to think we now strike a nice balance between zero hassle asset bundling and professional front-end engineers using phx.new and quickly getting to work.

Those were two separate points, I should have used a linebreak there in retrospect.

My point was that if you look at the changes and new features, all of it seems to me as stuff that improves core functionality, there's no feature creep.

Yay webpack because that's what I use so less work for me next time I start a new phoenix project (:

I don't love Webpack by any means, but it's a helluva lot better than the disaster that was Brunch.

(but hey, I'm still stuck back whenever Gulp was popular, so don't take me too seriously!)