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

jolly-bench

v0.1.0

Published

Load testing CLI built on jolly-coop

Readme

jolly-bench

Load testing CLI built on jolly-coop — structured concurrency for JavaScript.

A fixed number of virtual users hammer a target URL (or run a scenario module) for a fixed duration. Latency percentiles, throughput, and error breakdown are reported at the end. Partial results survive Ctrl-C.

Install

npm install -g jolly-bench

Requires Node 22+.

Usage

jolly-bench -u https://api.example.com -c 50 -d 30s
jolly-bench -u https://api.example.com -c 50 --rps 100 -d 1m
jolly-bench --scenario ./flow.mjs -c 100 -d 2m --out samples.ndjson

Flags

| Flag | Description | |---|---| | -u, --url <url> | target URL (GET by default) | | --scenario <path> | ESM module, default export async (user, signal) => void | | -c, --concurrency <n> | virtual user count (default 10) | | -d, --duration <dur> | run duration, e.g. 30s, 2m, 1h (default 30s) | | --rps <n> | target aggregate requests-per-second | | --per-request-timeout <dur> | per-request timeout (default 10s) | | --method <verb> | HTTP method (default GET) | | --header <k:v> | repeatable | | --body <str> | request body | | --user-agent <str> | (default jolly-bench/<version>) | | --out <path> | write per-request NDJSON samples | | --warmup <dur> | discard samples from first N seconds (default 0) |

Exit codes: 0 graceful, 1 fatal, 2 bad args, 130 Ctrl-C.

Example output

Running 30s test @ http://localhost:9999
  50 VUs, 1 thread

latency (ms):
  avg     42.1
  p50     38.3
  p95     89.4
  p99    142.7
  max    687.2

throughput:  1,187 req/s
total:       35,610 requests in 30.00s
success:     35,599 (99.97%)
errors:         11 (0.03%)
  TimeoutError:  8
  NetworkError:  3

status:
  200:       35,599

NDJSON samples

With --out samples.ndjson, one line per completed request:

{"ok":true,"t":0.142,"vu":7,"duration_ms":38.2,"status":200,"size":1843,"ts":"2026-04-17T..."}
{"ok":false,"t":0.191,"vu":3,"duration_ms":42.1,"error":"TimeoutError","message":"...","ts":"2026-04-17T..."}

Scenario modules

// flow.mjs
export default async function (user, signal) {
  const login = await fetch("https://api.example.com/login", { signal })
  const token = (await login.json()).token
  await fetch("https://api.example.com/me", { headers: { authorization: `Bearer ${token}` }, signal })
}

Pass signal to every cancellation-aware API inside the scenario — this is the jolly-coop contract and it lets jolly-bench cancel in-flight requests cleanly at deadline / Ctrl-C.

License

MIT