3 ms·
I find webpack to be quite a 'holistic' solution I got pretty much everything out of the box or with minimal googling. I agree though over-fragmentation is a h
by neilellis 10y ago
I find webpack to be quite a 'holistic' solution I got pretty much everything out of the box or with minimal googling.
I agree though over-fragmentation is a huge problem for JS, we need the big players (either foundations or companies) to put their weight behind one or two solutions and just get on with it :-)
- rpeden 10y agoGoogle sort of already has one, and has for a long time. Now that their Closure Compiler supports ES6 quite well, I've had a decent amount of success writing my app using straightforward ES6 and referencing the extensive Closure Library for functionality I would've previously pulled in npm packages for. And the nice thing is that the whole library is written in such a way that all of the compiler's advanced optimizations and branch pruning, and dead code elimination work nicely on it so your compiled JS ends up containing only the code you need, and none of the code your don't need. If you want to use JSX in React projects, you can still zip the code through Babel or Typescript before feeding it to Closure. It certainly won't work for every project, but it's one way to write modern JS without having to deal with the node/npm ecosystem too much...at least until things settle down a bit.