Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

https://what-problem-does-it-solve.com/webpack/interoperabil... nailed head-on what I detest about Webpack and many Javascript build solutions for that matter: the burning desire to shove the kitchen sink of operations into a single tool with its own, incompatible-with-everyone-else, plugin framework and an ungodly configuration language. Where all I really wanted was a somewhat more ergonomic Make and a bunch of well-written, decoupled tools to use with it.

This is on my back burner of ideas to run with one day, but as a back-end engineer working in other langs, it hasn't quite bubbled up to the surface yet.



Several of these exist and predate webpack. Webpack became popular precisely because it wasn't grunt, gulp or npm run scripts.


And yet, look what it has become.


Agreed. A decent build system language and separate tools would be a lot easier to understand than one megatool that does everything in a magic way with plugins and a mega-config file that's impossible to understand.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: