What is Brunch?
What is Grunt?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Brunch?
What are the cons of using Grunt?
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
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.
Grunt is all based on configuration. Some of the configuration is well documented, and some pre-built Gruntfiles can be dropped in and work like a charm. But if you are ever in the position where you have to make any changes to your large and complicated Gruntfile, set aside a few days to work on it. The deeper you get into it, the less intuitive you will find it, and the more strange behaviors you will find from plugins with some 'automagical' undocumented configuration or behavior. If you want a build process that you can understand, and that six months from now you will still understand, you are better off using Gulp.
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.
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.
Using ES7 async/await make the whole tooling chain "problem" disappear. No more code - no grunt tasks, no problems. We don't use grunt anymore.
We use it in development for the main application and is responsible for generating the Electron binary artifacts for the client application.
We use Grunt to automate some stuff, mostly related to tasks for the the Web App.