包详细信息

gulp-run-sequence

OverZealous3.7k不推荐使用0.3.2

Renamed to run-sequence as it's not really a gulp plugin.

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

自述文件

Deprecated - Please use run-sequence instead

gulp-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.

You can still run some of the tasks in parallel, by providing an array of task names.

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.

Usage

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

gulp.task('build', function(cb) {
  runSequence('build-clean', ['build-scripts', 'build-styles'], 'build-html', cb);
});

// configure build-clean, build-scripts, build-styles, build-html as you
// wish, but make sure they either return a stream or handle the callback
// Example:

gulp.task('build-clean', function() {
    return gulp.src('build').pipe(clean());
});

LICENSE

(MIT License)

Copyright (c) 2014 Phil DeJarnett

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

更新日志

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

2.2.1 - 2018-01-03

Changed

  • Replaced deprecated gulp-util with individual packages, thanks to @demurgos

2.2.0 - 2017-09-19

Changed

  • Fixed handling of orchestration aborted errors, thanks to @memoryhole

2.1.0 - 2017-07-24

Changed

  • Added options object
    • Added option for reduced stack trace reporting
    • Added option to ignore falsey task names

2.0.0 - 2017-06-30

Changed

  • Specified version numbers for all dependencies, due to Chalk dropping support for older Node versions

    This may be a breaking change if you depend on a newer release of any dependency, so you can continue using 1.2.2 in that case.

1.2.2 - 2016-06-29

Changed

  • Now passes the error back to GulpUtil.PluginError

1, 2, skip a few…


1.0.0 - 2014-09-29

Possible Breaking Change in version 1.0.0

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:

  1. Remove duplicate tasks if they are a mistake.
  2. Filter unneeded duplicate tasks before passing them to run-sequence.
  3. Rewrite your tasks or wrap your tasks within functions that can be called multiple times if for some reason you rely on this functionality.
  4. Continue using run-sequence version 0.3.7 if it was working for you.

Older

I'm not going to go through the old history at this point.