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

@x-oasis/push-stream

v0.13.0

Published

Single-consumer push-pull async stream with enqueue/done/error semantics (inspired by claude-code Stream<T>)

Readme

@x-oasis/push-stream

A single-consumer, push-pull bridged async stream. Modeled after claude-code's Stream<T> — a low-level transport pipe for producer-consumer event delivery.

Install

npm install @x-oasis/push-stream

Quick Start

import { PushStream } from '@x-oasis/push-stream';

const stream = new PushStream<string>();

// Producer side
stream.enqueue('hello');
stream.enqueue('world');
stream.done();

// Consumer side
for await (const value of stream) {
  console.log(value); // 'hello', 'world'
}

API

new PushStream<T>(options?)

Create a new stream.

| Option | Type | Description | |--------|------|-------------| | onReturn | () => void | Called when the consumer breaks out of iteration early. Use for cleanup (abort fetch, close socket, etc.). |

Producer API

| Method | Description | |--------|-------------| | enqueue(value: T) | Push a value. Delivered directly to a waiting consumer or buffered. Silently discarded after done() / error(). | | done() | Mark stream as completed. Pending and subsequent next() calls return { done: true }. | | error(err: unknown) | Terminate with error. Pending next() is rejected. Subsequent next() calls also reject with the stored error. |

Consumer API

| Method | Description | |--------|-------------| | [Symbol.asyncIterator]() | Returns AsyncIterableIterator<T>. Throws if called twice (single-consumer). | | next() | Pull next value. Resolves immediately if buffered, otherwise suspends. | | return() | Called on early break. Marks done and invokes onReturn. |

Introspection

| Property | Type | Description | |----------|------|-------------| | state | 'idle' \| 'flowing' \| 'error' \| 'done' | Current stream state. | | isDone | boolean | Whether terminated (by done(), error(), or return()). | | bufferedCount | number | Number of buffered values not yet consumed. | | hasWaiting | boolean | Whether a consumer is currently waiting for next(). |

Comparison with @x-oasis/event-stream

| Feature | PushStream | EventStream | |---------|-------------|--------------| | Completion | Explicit via done() | Event-driven via isComplete predicate | | Final result | None (pure transport) | result(): Promise<R> with extractResult | | Error handling | error() rejects pending + future next() | error() rejects result() promise | | Consumer enforcement | Strict single-consumer (throws) | Soft single-consumer (second gets empty) | | onReturn callback | Supported | Not supported | | Use case | Low-level pipe, resource cleanup | Structured event protocol with aggregation |

License

ISC