Need advice about which tool to choose?Ask the StackShare community!
gulp vs Webpack: What are the differences?
What is gulp? The streaming build system. Build system automating tasks: minification and copying of all JavaScript files, static images. More capable of watching files to automatically rerun the task when a file changes.
What is Webpack? A bundler for javascript and friends. A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
gulp and Webpack can be primarily classified as "JS Build Tools / JS Task Runners" tools.
"Build speed", "Readable" and "Code-over-configuration" are the key factors why developers consider gulp; whereas "Most powerful bundler", "Built-in dev server with livereload" and "Can handle all types of assets" are the primary reasons why Webpack is favored.
gulp and Webpack are both open source tools. Webpack with 49.8K GitHub stars and 6.27K forks on GitHub appears to be more popular than gulp with 31.3K GitHub stars and 4.41K GitHub forks.
Airbnb, Instagram, and Pinterest are some of the popular companies that use Webpack, whereas gulp is used by Mailgun, Sellsuki, and Movielala. Webpack has a broader approval, being mentioned in 2206 company stacks & 1338 developers stacks; compared to gulp, which is listed in 1163 company stacks and 705 developer stacks.
What is gulp?
What is Webpack?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose gulp?
- Build speed453
- Readable279
- Open source210
- Node streams175
- Intuitive107
Why do developers choose Webpack?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using gulp?
What are the cons of using Webpack?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with gulp?
What tools integrate with Webpack?
Sign up to get full access to all the tool integrationsMake informed product decisions
I use JavaScript these days and for few years I didn't have to use jQuery at all. I used to use it back in the days when IE8 and similar was a thing. But due to better browser support of native functions for DOM manipulation I could move to vanilla JavaScript. Most of the time, that's all I need to work with modals/accordions and similar. But I'm not saying that jQuery is bad. It was, and still is a great tool. Some of it's features are available in all browsers nowadays so it is not so important as it used to be. But jQuery has still advantage for example in it's selector engine, some DOM selections which are easy in jQuery are a bit more difficult in vanilla JS (you have to create some helper functions or use some 3rd party library to help you with that), but to be honest I needed this on very few occasions. So it really depends on your project (supported browses, plain JS or some bundling - gulp, Webpack, whether you plan to use modules etc.). Hope this helps.
Using Webpack is one of the best decision ever. I have used to Grunt and gulp previously, but the experience is not the same, and despite I know there are other bundlers like Parcel, Webpack gives me the perfect balance between automatization and configuration. The ecosystem of tools and loaders is amazing, and with WebPack #merge, you can modularize your build and define standard pieces to assemble different build configurations. I don't like processes where you cannot see their guts, and you have to trust in magic a little bit too much for my taste. But also I don't want to reinvent the wheel and lose too much time configuring my build processes. And of course, I love #WebPackDevServer and hot reloading.
gulpGulp is a new build system which shows a lot of promise. The use of streams and code-over-configuration makes for a simpler and more intuitive build. There isn't much boilerplate code so you're able to roll your own asset pipeline. Even if you don't know node.js streams, gulp is pretty readable and easier to understand.
PS: It's worth saying if you know Grunt then you can learn Gulp in a day.
gulpGulp is used as the build system for Cloudcraft.co with a lot of custom targets: vendoring dependencies, transpiling ES2015 to Ecmascript5 (with Babel), incremental compilation of multiple watched modules, minification, creation of app distribution packages etc. Having previously used Grunt, I've come to greatly prefer Gulp due to the ability to easily write my own tasks using plain JS without necessarily relying on plugins for everything.
WebpackWebpack is the best bundler. Period.
Yes, it has a(n arguably) messy documentation, and a steep learning curve; but once you get the hang of it, there is nothing you cannot do with it.
Use it and you don’t have to use any other bundler at all.
It has a vivid ecosystem, and great plugin support.
gulpgulp is used to package our plugins for the WSC (Woltlab Suite Core) in a fast, convenient and code-driven way. We enjoy the comfort it offers with stuff like the gzip-plugin or tar-packing.
gulpFor all our frontend site builds, Grunt allows us to do one-click builds for SASS, Coffeescript and other tools, with minifying and general restructuring built right in.
gulpgulp is a fancy alternative to grunt (that we don't use anymore). Just use async/await instead of "stream" everything (which is a nonsens). We don't use gulp.
gulpIf a project has a more complex build, gulp allows us to build a flexible build pipeline and automatically rebuild on files changes. Speeds up JS development.
WebpackMy preferred build tool; allows me to bundle my JSX, JS, CSS files for easy access and I can pass the bundle through my node server for server side rendering.
WebpackFlexible building and compiling of source for browser consumption, mainly for JS, but experimenting a little with CSS (although I prefer StylusJS for CSS).