4 ms·

Is something really wrong with WebPack? Didn’t we decide that we want more modularity and plugins, instead of “zero configuration” solutions that lock you into

Is something really wrong with WebPack? Didn’t we decide that we want more modularity and plugins, instead of “zero configuration” solutions that lock you into a few technologies? What about the next hip new frameworks that release in the future? Will they just be piled into parcel, or will they add a plugin system? This seems like an unsustainable model.

mattbreeden 8y ago
> or will they add a plugin system? https://parceljs.org/plugins.html https://parceljs.org/plugins.html
thatswrong0 8y ago
Caching and parallelization are my complaints with WebPack. WebPack doesn't cache that well out of the box, and plugins like HardSource seem to have errors often enough that they're kind of annoying. WebPack also doesn't have parallelization built in, so you need something like HappyPack. Maybe I was doing something stupid, but I wasn't able to get HappyPack and HardSource to work together nicely.
- ksec 8y ago
  >Caching and parallelization are my complaints with WebPack I thought those were fixed in v4?
  - thatswrong0 8y ago
    They made it faster, but per the V4 announcement: PS: we haven’t implemented Multicore, or Persistent Caching yet (slated for version 5). This means that there is still lots of room for improvement!!!! It _is_ coming, which I'm excited about. https://medium.com/webpack/webpack-4-released-today-6cdb994702d4 https://medium.com/webpack/webpack-4-released-today-6cdb9947...