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

stream-stack

v1.1.4

Published

Filter low-level `Stream` instances into stackable, protocol-based streams.

Readme

node-stream-stack

Filter low-level Stream instances into stackable, protocol-based streams.

This module exposes the StreamStack interface, which starts off as a node Stream subclass that accepts a "parent" Stream to work with. StreamStack is meant to be subclassed in order to implement the layers of a protocol, or run the parent Stream's data through some kind of filter (i.e. compression).

By default, a StreamStack instance proxies all events downstream (from the parent stream to the child stream), and proxies all functions calls upstream (from the child stream to the parent stream).

Keeping the StreamStack subclass' implementation independent of the parent Stream instance allows for the backend transport to be easily swapped out for flexibility and code re-use. For example, storing netcat results to a file, and using fs.ReadStream as your parent stream, rather than net.Stream, in your test cases.

Since StreamStack inherits from the regular node Stream, all it's prototypal goodies can be used along with your subclass instances. This makes it extremely easy for you to call Stream#pipe(writable), in order to utilize node's data transfer philosophies.

A Simple Example

Here's a simple, kinda silly example:

var util = require('util');
var StreamStack = require('stream-stack').StreamStack;

// The first argument is the parent stream
function DoubleWrite(stream) {
  StreamStack.call(this, stream);
}
util.inherits(DoubleWrite, StreamStack);

// Overwrite the default `write()` function to call
// write() on the parent stream twice!
DoubleWrite.prototype.write = function(data) {
  this.stream.write(data);
  this.stream.write(data);
}


// How to Use:
var doubleStdout = new DoubleWrite(process.stdout);
doubleStdout.write("this will be printed twice!\n");

We've defined a DoubleWrite class. It accepts a writable stream, and whenever write() is called on the DoubleWrite instance, then in return write() get called twice on the parent stream. In this example, our writable stream, process.stdout, will get the string printed to it twice.

Known Subclasses

Check out the Wiki page to see the list of Known Subclasses.