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.
In 2014, PagerDuty struggled with safely releasing reliable mobile applications to users due to some issues with how the code was being packaged and handled.
PagerDuty’s mobile apps are hybrid and used Cordova to share code between platforms. Coding was straightforward but packaging was not, as a separated Gulp-based build process was also being used. The PagerDuty team took a page from Java and started creating software artifacts.
Have had gulp in my build toolbox for years now. Sure all the cool kids are using Webpack etc now as do I on some projects, but I love how easy it is to knock up a config, to load the dependencies and to script the simple tasks we do most often (concat, lint check, sass, etc..) with an easily repeatable config style and less opacity than some of the heavy hitters. Might not have the one-stop-shop that the 800lb gorillas have but still relevant on the tool-belt
We use gulp because Django asset pipeline is nonexistent. We tried plugins such as django-compressor but they felt very short of what was desired, with key features, such as adding a map file, missing or difficult to handle.
With gulp, what was taking us days was solved in one afternoon.
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