What is gulp?
What is Parcel?
Want advice about which of these to choose?Ask the StackShare community!
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 Parcel?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Gulp 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.
love it！l like gulp‘s logo！
Gulp 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.
Webpack 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.
gulp 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.
For 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.
gulp 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.
If 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.
My 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.
Flexible building and compiling of source for browser consumption, mainly for JS, but experimenting a little with CSS (although I prefer StylusJS for CSS).
We use this to optimise the delivery of the client-side for our revised Admin System, so it's able to be delivered to browsers as efficiently as possible.