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

@zenfs/streams

v1.0.1

Published

A modern node:stream polyfill

Readme

ZenFS Streams

A modern polyfill for node:stream.

This package replaces readable-stream in ZenFS. readable-stream made up 10 of the 17 dependencies in the @zenfs/core tree and totaled 703 KB unpacked, and it has a number of unresolved problems with its types and legacy code.

It is written in TypeScript against Node's current implementation, and every exported class is declared implements its node:stream counterpart.

Usage

import { Readable, Writable, pipeline } from '@zenfs/streams';

await pipeline(
	Readable.from(['hello', ' ', 'world']),
	new Writable({
		write(chunk, encoding, callback) {
			console.log(chunk.toString());
			callback();
		},
	})
);

Notes

  • The only runtime dependency is buffer, which resolves to the built-in module on Node. events, process, abort-controller and string_decoder are not needed: EventEmitter and StringDecoder are implemented here, and AbortController and queueMicrotask are used directly.
  • StringDecoder decodes UTF-8 with a streaming TextDecoder. UTF-16LE is handled separately, since Node drops a trailing odd byte and preserves lone surrogates where the WHATWG decoder replaces both with U+FFFD.
  • Outside Node there is no process.nextTick, so callbacks fall back to queueMicrotask. Node drains its next-tick queue ahead of the microtask queue; the fallback has no equivalent, so those callbacks interleave with promise continuations rather than preceding them.
  • finished() on a WHATWG stream needs the closed-promise symbol that node:stream (and this package's toWeb()) attaches. A plain ReadableStream cannot be observed without consuming it, so it is rejected.
  • setMaxListeners is honored as state but never produces Node's MaxListenersExceededWarning.