Sync Gulp Tasks with run-sequence

By  on  

gulp.js is an awesome utility for so many things.  I've recently started using gulp as a build tool for the next blog redesign, whenever that may come.  In the past I had written my own build scripts but they quickly got messy and I ran into problems with concurrent tasks and knowing when each was complete.  gulp.js has made my build code prettier but I still get caught with timing issues due to async tasks.

Of course the nature of JS is becoming async but sometimes I just want a "top down" build process -- that's where run-sequence comes in.  With run-sequence I can easily group tasks to ensure they are done before setting off other tasks!

run-sequence works by passing arguments in the form of arrays or strings; an array signifies the tasks can be run concurrently, a string signifies a single task:

var runSequence = require('run-sequence');

gulp.task('some-task', function() {
		['task-1', 'task-2', 'task-3'], // These 3 can be done in parallel
		'task-4', // ...then just do this
		['task-5', 'task-5'], // ...then do these things in parallel
		'task-6', // ...then do this
		// ....

Each successive argument waits for the previous task(s) to finish.  My future theme's working gulp build file default task looks as follows:

// Create the default run action, which should be the entire build
gulp.task('default', function() {
		['copy-js-dir', 'copy-php-files', 'copy-image-files', 'compile-stylus'],
		['minify-css', 'minify-js'],

JavaScript purists will hate on me for not creating my own promises to avoid the need for sync and run-sequence, but to be honest, I don't care.  Adding my own promises would make the code messier and with little speed benefit.

Sometimes we have to make concessions for the sake of maintainability -- all developers know that.  run-sequence was a concession I've made to keep my code maintainable and logical in my own head.

Recent Features

  • By
    fetch API

    One of the worst kept secrets about AJAX on the web is that the underlying API for it, XMLHttpRequest, wasn't really made for what we've been using it for.  We've done well to create elegant APIs around XHR but we know we can do better.  Our effort to...

  • By
    CSS vs. JS Animation: Which is Faster?

    How is it possible that JavaScript-based animation has secretly always been as fast — or faster — than CSS transitions? And, how is it possible that Adobe and Google consistently release media-rich mobile sites that rival the performance of native apps? This article serves as a point-by-point...

Incredible Demos

  • By
    Making the Firefox Logo from HTML

    When each new t-shirt means staving off laundry for yet another day, swag quickly becomes the most coveted perk at any tech company. Mozilla WebDev had pretty much everything going for it: brilliant people, interesting problems, awesome office. Everything except a t-shirt. That had to change. The basic...

  • By
    MooTools Star Ratings with MooStarRating

    I've said it over and over but I'll say it again:  JavaScript's main role in web applications is to enhance otherwise boring, static functionality provided by the browser.  One perfect example of this is the Javascript/AJAX-powered star rating systems that have become popular over the...


  1. Pablo Perez

    Thanks for all your articles David!

  2. I recently came across Gulp and encountered the same issues… and found the same solution, before Gulp 4 is released !

    with run-sequence, I can even load/queue my tasks as modules and share them across different projects.

  3. Juha

    I’d add callback in tasks, at least for the sake of example – otherwise tasks depending on it would not wait until it is completed, right?

    gulp.task('some-task', function(done) {
      runSequence('task-1', ['task-2', 'task-3'], done);
  4. Damn, that’s awesome! I remember seeing this module a while back and not thinking much of it, but the feature you demonstrate where you can define subtasks to run in parallel is very impressive.

    Took two minutes to setup, works like a charm. Thanks for sharing :)

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!