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

wye

v0.1.0

Published

Pipe Arrays of Streams

Downloads

5

Readme

Wye Splitter for Node Streams

In plumbing, a wye fitting is used for splitting a stream into multiple streams or merging multiple streams into a single stream. The sole purpose of this module is to do exactly that.

What it looks like:

// upstream is the Readable stream (i.e. process.stdin)
// downstream is the Writable stream (i.e. process.stdout)
wye(upstream, downstream);

A Contrived Example:

var Transform = require('stream').Transform,
    // Let's create an array of transform streams
    tArr = [Transform(), Transform(), Transform()],
    wye = require('wye.js');

// Attach the required _transform method to each stream
// Node API Docs has more info on Transform streams...
tArr.forEach(function (val, ind, arr) {

  // Do some trivial stuff to show things work...
  // This will append some text to the chunk, so
  // you know what stream it came from. 
  tArr[ind]._transform = function (chunk, encoding, done) {
    chunk = 'tArr' + ind + ': ' + chunk;
    tArr[ind].push(chunk);
    done();
  };

});

// Now we use the wye splitter to pipe our array of streams

// stdin --pipe--> stream array
wye(process.stdin, tArr);

// stream array --pipe--> stdout
wye(tArr, process.stdout);

You can also pipe arrays of streams to arrays of streams in the same manner.

streamArray1 = [stream1, stream2, stream3];
streamArray2 = [stream4, stream5, stream6];

// wye will handle all of the piping
wye(streamArray1, streamArray2);

The above example achieves the same as:

stream1.pipe(stream4);
stream1.pipe(stream5);
stream1.pipe(stream6);
stream2.pipe(stream4);
stream2.pipe(stream5);
stream2.pipe(stream6);
stream3.pipe(stream4);
stream3.pipe(stream5);
stream3.pipe(stream6);

Just because...

wye(process.stdin, process.stdout);

// is the same as...

process.stdin.pipe(process.stdout);

Wye not?