3 ms·

I've used Webpack on and off since v2 and I'm still no fan. If I'm being honest, there's been times that it's perhaps been the worst dev experience I've endure

• thelarkinn 9y ago
  Sure, but since your experience is not configuring anything, how are you going to know what it's actually doing to your code. And what are the tradeoffs? Seems like many don't have this answer because they don't have good archetectural reasons for choosing it.
  • BigJono 9y ago
    For what it's worth, my experience with Parcel so far has been a show stopping bug that makes CSS Modules unusable with it, was quite difficult to diagnose (as with any bug in a dependency, I spent yonks looking at my own codebase), and has so far gone un-fixed. https://github.com/parcel-bundler/parcel/issues/378 https://github.com/parcel-bundler/parcel/issues/378 I don't see how this is really possible given the relatively high usage level of CSS Modules, but whatever. I'm forced to stick with Webpack for the time being.
• conradfr 9y ago
  There is side projects that I literally don't start because I don't want to deal with Webpack and Babel (I don't think I have ever had a project where Babel wasn't complaining it was out of date even on greenfield install). Another complaint for me is how all tutorials, boilerplates etc mingle nodejs server and react/angulas/vue deps and code where all I want is frontend code and build and I have to remove things by trial and error.