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

async-iterables

v1.0.5

Published

Controlled async iterable – push values in, and receive feedback with for-of.

Readme

async-iterables

Controlled async iterable.

const items = createAsyncIterable<number>(controller => {
  doStuffWithCallback(async result => {
    await controller.yield(...)
    await controller.yield(...)
    await controller.return()
  })
})

You should always call controller.return if you want your iterable to finish eventually.

Examples

Adapting a Node EventEmitter (or Readable stream) that emits data, end, and error:

import { EventEmitter } from "node:events"
import { createAsyncIterable } from "async-iterable"

function fromEvents<T>(emitter: EventEmitter) {
	return createAsyncIterable<T, void, void>(controller => {
		const onData = async (chunk: T) => {
			const res = await controller.yield(chunk)
			if (res.done) {
				// consumer stopped (break/return)
				teardown()
			}
		}

		const onEnd = async () => {
			teardown()
			await controller.return()
		}

		const onError = async (err: unknown) => {
			teardown()
			await controller.throw(err)
		}

		const teardown = () => {
			emitter.off("data", onData)
			emitter.off("end", onEnd)
			emitter.off("error", onError)
		}

		emitter.on("data", onData)
		emitter.once("end", onEnd)
		emitter.once("error", onError)
	})
}

// Usage
const ee = new EventEmitter()

queueMicrotask(() => {
	ee.emit("data", 1)
	ee.emit("data", 2)
	ee.emit("end")
})

for await (const x of fromEvents<number>(ee)) {
	console.log(x)
}

API

createAsyncIterable<T = unknown, R = void, N = void>(
  callback: (controller: IteratorController<T, R, N>) => unknown,
): AsyncGenerator<Awaited<T>, Awaited<R>, N>

controller methods:

  • yield(value): Queue a value for the consumer. Resolves to IteratorResult<N, undefined>; done:true means the consumer is finished.
  • yieldIterable(iterable): Yield each value from another Iterable/AsyncIterable until done.
  • return(value): Finish the sequence with a return value.
  • throw(error): Error the sequence; the consumer will see the throw.

License

ISC