A Gulp plugin to execute functions within a Gulp task pipeline.
Go to file
2016-04-07 13:50:00 +02:00
dist fixes #3 and removes beautylog dependency 2016-04-04 22:32:30 +02:00
test added forFirst 2016-03-26 17:22:46 +01:00
ts fixes #3 and removes beautylog dependency 2016-04-04 22:32:30 +02:00
.gitignore added forFirst 2016-03-26 17:22:46 +01:00
.npmignore updated deps 2016-04-05 00:59:21 +02:00
.travis.yml update travis 2016-02-01 03:45:13 +01:00
LICENSE.md Update LICENSE.md 2015-09-03 20:20:41 +02:00
npmts.json add npmts.json 2016-02-12 05:41:02 +01:00
package.json fixed package.json 2016-04-07 13:50:00 +02:00
README.md fix Readme issue 2016-04-04 22:43:26 +02:00

gulp-function

accepts call to execute in gulp pipeline.

Status

Build Status Dependency Status bitHound Dependencies bitHound Code codecov.io

Version

GitHub version npm version

Usage

var gulp = require("gulp");
var gulpFunction = require("gulp-function");
var Q = require("q");

var myFunction = function () {
    var done = Q.defer();
    console.log("Hello World!")
    
    // NOTE:
    // you can use done.resolve as callback function
    // of any async tasks within this function
    done.resolve();
    
    return done.promise;
}

gulp.task('gulpTest',function() {
    var stream = gulp.src('./mydir/*.something')
        .pipe(gulpFunction(myFunction,'forEach')) //read the notes below
        .pipe(gulp.dest("./build/"));
    return stream; // by returning the stream gulp knows when our task has finished.
});

Notes:

  • The first argument of gulpFunction can also be an array of multiple functionnames. Each function can return a promise. the pipe stop will finish when every promise is fullfilled.
  • the second argument can be empty, it defaults to "forEach"
  • the following options are available:
    • "forFirst" - executes when first chunk/vinylfile of the stream reaches the pipestop. file is pushed further down the line when function's returned promise is fullfilled.
    • "forEach" - executes like "forFirst" but with every chunk/vinylfile in the stream;
    • "atEnd" - executes after all chunks have passed and are processed in full. That means the stream's "finish" event fires before "atLast" is executed!!!