6 ms·
Woof sometimes HN can be pretty unforgiving. Remember the human guys. Good job man. Keep it up. Thanks for contributing to open source.
by BucketSort 8y ago
Woof sometimes HN can be pretty unforgiving. Remember the human guys. Good job man. Keep it up. Thanks for contributing to open source.
- nikkwong 8y agoAgreed. Webpack's configuration is so daunting that, well, this is so obviously needed.
- chrisweekly 8y agoNot anymore! Webpack 4 is ~"zero-config"!
- kn8 8y agoFor a different definition of zero though. While webpack now does something useful with no configuration (which is great), you will most likely end up adding lots of configuration for any application. Whereas with jetpack there's a chance that you won't (at least in my experience). The challenge of course is the diversity of the ecosystem. Different projects are trying to address it differently, e.g. * CRA is opinionated and unconfigurable * Neutrino/pwa-cli propose a higher level plugin approach (i.e. install a plugin, without needing to configure it, in webpack plugins take many lines of configuration to configure) * Next/Gatsby use a plugin system as well but are also specialised tools which means a lot of decisions can be abstracted * jetpack tries to be application/use case/framework agnostic and provide you with the most commonly used/useful foundation, you can optionally add extra (e.g. sass), but you don't have to recreate the foundation (i.e. es6, jsx, modern css, css modules, hot reloading, serving, producing html, etc) It's also about the DX, jetpack lets you run a dev server with a single command, it lets you analyse the bundle with a sigle command, it builds an optimised, split chunk bundle with a single command. Just pointing out some motivations behind the project, I'm a fan of webpack, been using it for many years.