0.1.3 • Published 6 years ago

gulp-multistream v0.1.3

Weekly downloads
109
License
ISC
Repository
github
Last release
6 years ago

gulp-multistream

travis cov-codeclimate score-codeclimate npm-downloads npm-version dm-david ISC License Analytics

Install:

npm install -D gulp-multistream

Use:

var multistream = require('gulp-multistream');

gulp.task('doStuff', function() {
  return gulp.src('myfile.js')
    .pipe(doTheStuff())
    .pipe(multistream( gulp.dest('dest1'), gulp.dest('dest2') );
});

And just in case you missed the significance, here's another example:

var multistream = require('gulp-multistream');

gulp.task('doStuff', function() {
  var destinations = [];

  if (useDest1) { destinations.push( gulp.dest('dest1') ); }
  if (useDest2) { destinations.push( gulp.dest('dest2') ); }
  if (useDest3) { destinations.push( gulp.dest('dest3') ); }

  // Do we have 1, 2, or 3 destinations?
  // Why should I have to care at this point?

  return gulp.src('myfile.js')
    .pipe(doTheStuff())
    .pipe(multistream.apply(undefined, destinations));
});

But why:

Well, I had a build that needed to build some modules, concat, and output to 15 different folders. Except, when it needed to output to 10 folders. Or when it needed to output to 8 folders. I think you get the idea. And then I wrote 12 more such tasks, that copy to 15, 10, or 8 folders... sometimes. And, well, I refuse to maintain hardcoded destinations for that. gulp-multistream to the rescue.

If you find a great use for this that is not fully supported by the exact 20 lines of this plugin, please feel free to submit an issue.

0.1.3

6 years ago

0.1.2

7 years ago

0.1.1

7 years ago

0.1.0

9 years ago

0.0.3

9 years ago

0.0.2

9 years ago

0.0.1

9 years ago