@bearly/pacing

中文文档
0.2.0发布于 2026/09/27MITTypeScriptES Module零依赖近 30 天下载 6526

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

原始使用文档
文档目录3 节
  1. Install
  2. Use
  3. Guarantees

@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.

版本与发布记录

@bearly/pacing 共发布 2 个版本,首次发布于 2026/09/25;过去 12 个月发布了 2 个版本。

版本发布日期距今
0.2.0latest2026/09/271 个月前
0.1.02026/09/251 个月前

关于 @bearly/pacing 的常见问题

@bearly/pacing 是什么?

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

如何安装 @bearly/pacing?

在项目目录运行 npm install @bearly/pacing,或使用 pnpm add / yarn add / bun add。

@bearly/pacing 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@bearly/pacing 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@bearly/pacing 可以商用吗?

@bearly/pacing 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@bearly/pacing 的下载量有多少?

根据 npm 官方下载统计,@bearly/pacing 在 2026/10/08 – 2026/11/06 这 30 天内被下载 6,526 次,日均约 218 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@bearly/pacing 还在维护吗?

最新版本 0.2.0 发布于 2026/09/27(1 个月前);至今共发布 2 个版本,其中过去 12 个月发布了 2 个;首次发布于 2026/09/25。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。