@haatlabs-core/providers

中文文档
0.18.5发布于 2026/11/14Apache-2.0TypeScriptESM + CJS近 30 天下载 6441

Retry, circuit breaker, rate and concurrency limits for calling outside services.

原始使用文档

@haatlabs-core/providers

What every caller of an outside service needs, written once: retry, a circuit breaker, rate-limit turns, a concurrency limit and mapLimit, protect (the layers in their order), the services-gateway contract (tiers and the headers a gateway reads), cachedCall with single-flight, and the safe fetch of untrusted URLs (@haatlabs-core/providers/safe-fetch). Each takes any call; the error a project throws stays the project's. It throws PROVIDER_UNAVAILABLE by default; a project spreads PROVIDERS_ERRORS into defineErrors.

const breaker = createCircuitBreaker({ name: 'search' });
const gate = gateByRateLimit(limiter, { key: 'search', policy }, (ms) => refusal(ms));
const answer = await protect(() => call(), { gate, breaker, retry: { signal } });

The root carries cachedCall, the codecs and the memory store, never the Redis one: import createRedisCacheStore from @haatlabs-core/providers/cache, so the root's types never name ioredis. The root loads no HTTP client either; sniffImageType is there as well as in @haatlabs-core/providers/safe-fetch.

A fetch that failed for now (DNS, a reset, a 5xx or 429 image) is worth another attempt:

import { isTransientSafeFetchError, safeFetchImage } from '@haatlabs-core/providers/safe-fetch';
const image = await retry(() => safeFetchImage(url, { signal }), {
  isRetryable: isTransientSafeFetchError,
  signal,
});

localTimeoutMs(timeoutMs, call) bounds an adapter's own timeout by the call's deadline, and retryAfterMsOf(response.headers) reads a Retry-After (seconds or a date, at most 300 s).

@haatlabs-core/providers/contracts (0.12.1): PROVIDERS_ERRORS, ProviderErrorCode and createProviderError, and the services-gateway contract (SharedTier, SharedPriority, CallContext, sharedTierMap, bestTier, gatewayHeaders, GATEWAY_HEADER, UpstreamStatusError), with nothing of Node, undici or the tracing SDK: a project's contracts, which its pages load, import from here and never the root, which is for Node. Safe fetch loads undici only when it sends a request.

Install

pnpm add @haatlabs-core/providers

It leaves one package to your app, so the app holds one copy: ioredis.

版本与发布记录

@haatlabs-core/providers 共发布 27 个版本,首次发布于 2026/10/23;过去 12 个月发布了 27 个版本。

版本发布日期距今
0.18.5latest2026/11/143 天前
0.18.42026/11/133 天前
0.18.32026/11/134 天前
0.18.22026/11/134 天前
0.18.12026/11/134 天前
0.18.02026/11/134 天前

关于 @haatlabs-core/providers 的常见问题

@haatlabs-core/providers 是什么?

Retry, circuit breaker, rate and concurrency limits for calling outside services.

如何安装 @haatlabs-core/providers?

在项目目录运行 npm install @haatlabs-core/providers,或使用 pnpm add / yarn add / bun add。

@haatlabs-core/providers 支持 TypeScript 吗?

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

@haatlabs-core/providers 支持 ESM 还是 CommonJS?

同时提供 ES Module 与 CommonJS 入口,import 和 require() 都可以使用,打包工具会自动选择合适的版本。

@haatlabs-core/providers 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=24。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@haatlabs-core/providers 可以商用吗?

@haatlabs-core/providers 使用 Apache-2.0 许可。宽松许可:允许商业使用、修改和再分发,并附带明确的专利授权;分发时需保留许可与 NOTICE 文件,修改过的文件要注明改动。以上为概括,不构成法律意见,请以许可原文为准。

@haatlabs-core/providers 的下载量有多少?

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

@haatlabs-core/providers 还在维护吗?

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