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

@scramjet/ofca

v0.2.0

Published

Ordered flow with callback-first concurrent arrival

Readme

OFCA

OFCA mascot

Ordered concurrent work for Node.js >=22.

Why

Stream processing does not have to mean processing one item at a time. When each item can be handled independently, waiting for one result before starting the next leaves useful work idle.

How

OFCA applies a work step to every input chunk with a bounded amount of concurrency, then combines completed results in their original input order. It works with arrays, sync and async iterables, and Node Readables through async iteration—without being a stream class.

It sits between Array.prototype.map and Transform streams: it keeps map-like work composition while accepting unbounded data from streams.

What

OFCA (Ordered Flow with Concurrent Arrival) is a small standalone ESM library with zero runtime dependencies. It provides:

  • ofca(source, mapper, { concurrency }) for ordered asynchronous processing;
  • ofcaSync(source, stages) for synchronous iterable processing;
  • compose(...stages) for ordered unary stage composition; and
  • DROP for intentionally omitting an output.
import { DROP, compose, ofca, ofcaSync } from "@scramjet/ofca";

const doubleThenAdd = compose((value) => value * 2, (value) => value + 1);
console.log(ofcaSync([1, 2], doubleThenAdd)); // [3, 5]

const output = [];
for await (const value of ofca([1, 2, 3], async (value) => (
  value === 2 ? DROP : value * 10
), { concurrency: 2 })) {
  output.push(value);
}
console.log(output); // [10, 30]

See DEVELOPMENT.md for development instructions.

Representative benchmark

Run npm run benchmark to measure the current checkout. Results are configuration-specific (Node version, machine, workload, and concurrency) and are not an intrinsic or universal speedup claim.

What to expect

On Node v22.22.1, a 10,000-item workload with 16 async stages, small deterministic jitter, and OFCA concurrency of 256 completed in:

| Method | Time | Throughput | | --- | ---: | ---: | | Array.map ×16 + Promise.all | 140ms | 71,267 items/s | | OFCA | 971ms | 10,301 items/s | | 16 chained Node Transforms | 14.4s | 696 items/s |

OFCA is slower than unbounded array admission, while processing stream-sized input about 14.8× faster than the equivalent chained Transform pipeline in this run.