This was forked so we could use the chalk dependency at version 1.1.1. This specific version is needed because our repos mrr-static and tcb-static are running on an old version of node 0.10.45 and cannot use node libraries that have ES6 syntax. The later versions of chalk and later versions of run-sequence use ES6.
Runs a sequence of gulp tasks in the specified order. This function is designed to solve the situation where you have defined run-order, but choose not to or cannot use dependencies.
This is intended to be a temporary solution until the release of gulp 4.0 which has support for defining task dependencies in series or in parallel.
Be aware that this solution is a hack, and may stop working with a future update to gulp.
Each argument to run-sequence is run in order. This works by listening to the task_stop and task_err events, and keeping track of which tasks have been completed. You can still run some of the tasks in parallel, by providing an array of task names for one or more of the arguments.
If the final argument is a function, it will be used as a callback after all the functions are either finished or an error has occurred.
In version 1.0 I've added a check that prevents the same task from showing up within any sequence. This is to help reduce typo errors, as well as prevent the silent exit bug when the same task occurred twice in a parallel sequence. The sequence will now fail immediately during the validation stage.
If this breaking change affects you, you'll need to take one of several actions:
- Remove duplicate tasks if they are a mistake.
- Filter unneeded duplicate tasks before passing them to
run-sequence. - Rewrite your tasks or wrap your tasks within functions that can be called multiple times if for some reason you rely on this functionality.
- Continue using
run-sequenceversion 0.3.7 if it was working for you.
I welcome feedback if this change is a problem for your setup!
First, install run-sequence as a development dependency:
npm install --save-dev run-sequenceThen add use it in your gulpfile, like so (note these are only examples, please check the documentation for your functions for the correct way to use them):
var gulp = require('gulp');
var runSequence = require('run-sequence');
var del = require('del');
var fs = require('fs');
// This will run in this order:
// * build-clean
// * build-scripts and build-styles in parallel
// * build-html
// * Finally call the callback function
gulp.task('build', function(callback) {
runSequence('build-clean',
['build-scripts', 'build-styles'],
'build-html',
callback);
});
// configure build-clean, build-scripts, build-styles, build-html as you wish,
// but make sure they either return a stream or promise, or handle the callback
// Example:
gulp.task('build-clean', function() {
// Return the Promise from del()
return del([BUILD_DIRECTORY]);
// ^^^^^^
// This is the key here, to make sure asynchronous tasks are done!
});
gulp.task('build-scripts', function() {
// Return the stream from gulp
return gulp.src(SCRIPTS_SRC).pipe(...)...
// ^^^^^^
// This is the key here, to make sure tasks run to completion!
});
gulp.task('callback-example', function(callback) {
// Use the callback in the async function
fs.readFile('...', function(err, file) {
console.log(file);
callback();
// ^^^^^^^^^^
// This is what lets gulp know this task is complete!
});
});If you have a complex gulp setup with your tasks split up across different files, you may get the error that run-sequence is unable to find your tasks. In this case, you can configure run-sequence to look at the gulp within the submodule, like so:
// submodule tasks/mygulptask.js
var gulp = require('gulp'), // might be a different instance than the toplevel one
// this uses the gulp you provide
runSequence = require('run-sequence').use(gulp);
// ...and then use normally
runSequence('subtask1', 'subtask2');