npmpackage.info

Gathering detailed insights and metrics for run-sequence

Other packages similar to run-sequence

gulp4-run-sequence

1.0.2

Drop-in replacement for run-sequence for gulp 4

gulp-run-sequence

0.3.2

Deprecated - Please use run-sequence instead: https://npmjs.org/package/run-sequence

@types/run-sequence

2.2.0

TypeScript definitions for run-sequence

gulp-sequence

1.0.0

Run a series of gulp tasks in order.

run-sequence

Run a series of dependent gulp tasks in order

2.2.1

959

MIT

JavaScript

3.93 kB

100,289,416 2

Installations

npm install run-sequence

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Min. Node Version

>= 0.8.0

Node Version

9.3.0

NPM Version

5.6.0 Pull Requests

Open

0

Total

26

Closed

12

Merged

14

Issues

Open

0

Total

81

Closed

81

Releases

Unable to fetch releases

Contributors

Unable to fetch Contributors

View all 13 contributors

Languages

JavaScript

JavaScript (100%)

Love this project? Help keep it running — sponsor us today! 🚀

Developer

OverZealous

Download Statistics

Total Downloads

100,289,416

Last Day

27,467

Last Week

27,467

Last Month

397,051

Last Year

6,732,565

GitHub Statistics

959 Stars

91 Commits

56 Forks

15 Watching

1 Branches

13 Contributors

Bundle Size

10.51 kB

Minified

3.93 kB

Minified + Gzipped

Bundlephobia

Maintainers

Package Meta Information

Latest Version

2.2.1

Package Id

run-sequence@2.2.1

Size

5.74 kB

NPM Version

5.6.0

Node Version

9.3.0

Publised On

03 Jan 2018

Total Downloads

Cumulative downloads

Total Downloads

100,289,416

Last day

27,467

Compared to previous day

Last week

-64.2%

27,467

Compared to previous week

Last month

-1.7%

397,051

Compared to previous month

Last year

-17.1%

6,732,565

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

chalk fancy-log plugin-error

Dev Dependencies

gulp mocha should

Versions

run-sequence

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.

Is your company hiring Node developers?

If you are hiring developers, you can support this project and future open source work by checking out our company, Qualified.io.

Qualified is a service for online skills-assessment that can help you easily vet developers across a wide range of real-world programming skills.

Please help support this project, and sign up for a free trial.

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.

Please Note

This was intended to be a temporary solution until the release of gulp 4.0 which should have support for defining task dependencies similarly.

Given that Gulp 4 appears to never be fully released, take that for what you will. Be aware that this solution is a hack, and may stop working with a future update to gulp.

Usage

First, install run-sequence as a development dependency:

1npm install --save-dev run-sequence

Then 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):

1var gulp = require('gulp');
2var runSequence = require('run-sequence');
3var del = require('del');
4var fs = require('fs');
5
6// This will run in this order:
7// * build-clean
8// * build-scripts and build-styles in parallel
9// * build-html
10// * Finally call the callback function
11gulp.task('build', function(callback) {
12  runSequence('build-clean',
13              ['build-scripts', 'build-styles'],
14              'build-html',
15              callback);
16});
17
18// configure build-clean, build-scripts, build-styles, build-html as you wish,
19// but make sure they either return a stream or promise, or handle the callback
20// Example:
21
22gulp.task('build-clean', function() {
23    // Return the Promise from del()
24    return del([BUILD_DIRECTORY]);
25//  ^^^^^^
26//   This is the key here, to make sure asynchronous tasks are done!
27});
28
29gulp.task('build-scripts', function() {
30    // Return the stream from gulp
31    return gulp.src(SCRIPTS_SRC).pipe(...)...
32//  ^^^^^^
33//   This is the key here, to make sure tasks run to completion!
34});
35
36gulp.task('callback-example', function(callback) {
37    // Use the callback in the async function
38    fs.readFile('...', function(err, file) {
39        console.log(file);
40        callback();
41//      ^^^^^^^^^^
42//       This is what lets gulp know this task is complete!
43    });
44});

Using within gulp submodules

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:

1// submodule tasks/mygulptask.js
2
3var gulp = require('gulp'), // might be a different instance than the toplevel one
4    // this uses the gulp you provide
5    runSequence = require('run-sequence').use(gulp);
6    
7    // ...and then use normally
8    runSequence('subtask1', 'subtask2');

Options

There are a few global options you can configure on the runSequence function.

Please note these are global to the module, and once set will affect every use of runSequence.

Usage:

1var runSequence = require('run-sequence');
2runSequence.options.ignoreUndefinedTasks = true;
3gulp.task('task', function(cb) {
4	runSequence('foo', null, 'bar'); // no longer errors on `null`
5})

showErrorStackTrace: When set to false, this suppresses the full stack trace from errors captured during a sequence.
ignoreUndefinedTasks: When set to true, this enables you to pass falsey values in which will be stripped from the task set before validation and sequencing.

LICENSE

MIT License

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

2

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2

/10

Last Scanned on 2025-02-03

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More