DevOps / Build, Test, Deploy / JS Build Tools / JS Task Runners

Decision about Google Analytics, JavaScript, GitHub, GitHub Pages, gulp, Bootstrap, HTML5

Avatar of omidfarhang
Sr. Full Stack Developer ·

Developing static sites like a landing page for mobile app or just a personal resume using HTML5 and Bootstrap is a lot fun when you are using build tools like gulp . I made a personal resume using above tools and published them on GitHub Pages. It was fast and easy, Thanks to GitHub for the free service. All the JavaScript codes worked perfectly after being concat and minified and uglified by gulp and running perfectly on GitHub Pages. gulp created sitemap and inserted Google Analytics code into all pages and saved about 30% of images size by compressing them during build.

11 upvotes·2 comments·29.9K views

Decision about Webpack, gulp, jQuery, JavaScript

Avatar of Pustelto

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.

6 upvotes·3.9K views

Decision about Parcel, gulp, Grunt, Webpack, WebPackDevServer, Merge

Avatar of timbergus
Web UI Developer at Globant ·

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.

4 upvotes·4.1K views

Decision at PagerDuty about CoffeeScript, gulp, GitHub

Avatar of stackbot

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.

Rather than checking in transformed code or publishing modules to NPM, the team started creating zipped-up build artifacts, which coincided perfectly with GitHub's Releases feature which arrived in 2013. So despite JavaScript lacking a standard packaged app format like a JAR, PagerDuty was still able to improve the build times and sizes of their mobile apps.

4 upvotes·1.7K views

Decision about gulp

Avatar of deeknow
Systemic Solutions ·

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

3 upvotes·2.2K views

Decision at Pluckd about gulp

Avatar of Brauhaus

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.

2 upvotes·1.8K views

Decision about gulp

Avatar of nesterow
Software Engineer at Betwinner ·

I use gulp because so far it is self-explanatory and easy to scale

2 upvotes·59 views

Decision at Cloudcraft about gulp

Avatar of tjunnone

Gulp is used as the build system for 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

1 upvote·965 views

Decision at RocketFuel about gulp

Avatar of Vanuan

Gulp is used for writing transpiling, bundling, minification, watching and other tasks. gulp

1 upvote·540 views