4 ms·
Am I the only person who just doesn't get the appeal of Webpack over using something like Gulp? It just seems to me like Gulp is so much easier to use and setup
by JoshGlazebrook 10y ago
Am I the only person who just doesn't get the appeal of Webpack over using something like Gulp? It just seems to me like Gulp is so much easier to use and setup.
- dsego 10y agoWebpack does a lot more. Gulp is just a glorified (and cross-platform) make.
- JoshGlazebrook 10y agoI guess I meant more from a ease of use point of view. Gulp/Grunt are easier to configure and get going.
- dsego 10y agoNot that I have too much experience with either. But one example is having one webpack configuration with misc. loaders vs. reinventing it yourself and ending up with this mess: 1) You still get a config file, neat right https://github.com/mgechev/angular2-seed/blob/master/tools/config/seed.config.ts https://github.com/mgechev/angular2-seed/blob/master/tools/c... 2) And this boilerplate https://github.com/mgechev/angular2-seed/tree/master/tools/tasks/seed https://github.com/mgechev/angular2-seed/tree/master/tools/t...
- hokkos 10y agoWith gulp you rewrite webpack in every project. no thanks.
- kevindeasis 10y agoWebpack is amazing. You can even use Gulp with Webpack. Both are not identical tools.
- kuon 10y agoI just discovered brunch and it works well for me.
- tboyd47 10y agoWebpack isn't like Gulp at all. It's absolutely insane what Webpack can do. It can solve any asset-related problem imaginable. Compile SCSS into CSS into JSON and require it in your Javascript? Convert SVG images into data-URLs that work on all browsers? Manage async dependencies in your JS code without dynamic script tags or global variables? Automatically figure out exactly which assets you need on which page and chunk them all together? All of the above.