npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2023 – Pkg Stats / Ryan Hefner




wrap a readable/writable stream to be read-only





wrap a readable/writable stream to be read-only to prevent mucking up the input side

build status


Suppose you have a module that uses a readable/writable stream internally but want to expose just the readable part of that internal stream. This is common if you use the writable side internally and expose the readable side as the interface.

Now we can write some code like this with a through stream internally for convenience:

var through = require('through2');
var readonly = require('read-only-stream');

module.exports = function () {
    var stream = through();
    return readonly(stream);

but consumers won't be able to write to the input side and break the api:

var wrap = require('./wrap.js');
var ro = wrap(); // can't write to `ro` and muck up internal state


var readonly = require('read-only-stream')

var ro = readonly(stream)

Return a readable stream ro that wraps the readable/writable stream argument given to only expose the readable side.

stream can be a streams1 or streams2 stream.


With npm do:

npm install read-only-stream