npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

gulp-multistream

v0.1.3

Published

Write data to multiple streams in the pipeline, at the same time.

Readme

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.