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

@bearly/pacing

v0.2.0

Published

Pure pacing policy: full, additive and decorrelated jitter, and a readiness gate

Readme

@bearly/pacing

Pure pacing policy for reconnect and restart loops: when to try again, and when a dependency is ready.

Nothing here owns a clock, a timer, a socket or a process. You pass now, sleep, your probe and, in tests, a seeded random source. The module holds the common jitter patterns and a readiness gate in one place, so every loop can use the same code.

Install

Install from npm; a git install resolves the TypeScript source and runs only under Bun.

bun add @bearly/pacing

Use

import { additiveJitter, awaitReady, decorrelatedJitter, fullJitter } from "@bearly/pacing"

// Full jitter: uniform in [0, min(cap, base * 2 ** attempt)]. A plain spread over a window is base = cap = window.
const delay = fullJitter(250, 30_000, attempt)

// Additive jitter: keep the exponential delay as a floor and spread up to 25% above it, clipped to cap.
const quotaDelay = additiveJitter(60_000, 3_600_000, attempt, 0.25)

// Decorrelated jitter: uniform in [base, min(cap, previous * 3)]; feed back the last delay (base on the first call).
let wait = 500
wait = decorrelatedJitter(500, 30_000, wait)

// Readiness gate: probe until it answers true or the timeout (a duration) passes.
const outcome = await awaitReady(() => daemon.ping(), {
  timeoutMs: 30_000,
  retryMs: 250,
  now: () => Date.now(),
  sleep: (ms) => new Promise((resolve) => setTimeout(resolve, ms)),
})
if (!outcome.ready) console.warn(`daemon not ready after ${outcome.waitedMs} ms`, outcome.lastError)

awaitReady probes once at once, with no sleep. It then sleeps by decorrelated jitter between retryMs and maxRetryMs (default retryMs * 8), clipped so it never sleeps past the timeout. The last probe runs at or before the timeout, and ready: false comes back only after it. A probe that throws counts as not ready, and its last error is returned.

Choose additive jitter when a retry must wait at least its exponential base, full jitter when the whole delay can spread from zero, and decorrelated jitter when peers pace from their previous delay under contention.

The probe must bound itself. The gate checks the timeout only between probes, so a probe that never settles holds the gate past its timeout, forever. Give every probe its own timeout, shorter than timeoutMs: a call timeout on the socket, or an AbortSignal.timeout on the fetch.

Every function throws RangeError when its bounds name no delay (a negative base, a cap below base, a fractional attempt, an additive ratio outside [0, 1], or a bound that is not a finite number).

Guarantees

  • A delay never exceeds its cap; additive jitter never falls below its exponential floor, and decorrelated jitter never falls below its base.
  • The readiness gate never sleeps past its timeout. It returns at the timeout when every probe settles.
  • No I/O, timers or globals. Math.random is the default random source, and every function takes a replacement.