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

@http-client-toolkit/core

v3.0.0

Published

Core HTTP client with pluggable caching, deduplication, and rate limiting

Readme

@http-client-toolkit/core

Core HTTP client with pluggable caching, deduplication, and rate limiting. Part of the http-client-toolkit monorepo.

Installation

npm install @http-client-toolkit/core

Requires Node.js >= 20.

You'll also need at least one store backend:

npm install @http-client-toolkit/store-memory
# or
npm install @http-client-toolkit/store-sqlite

Quick Start

import { HttpClient } from '@http-client-toolkit/core';
import {
  InMemoryCacheStore,
  InMemoryDedupeStore,
  InMemoryRateLimitStore,
} from '@http-client-toolkit/store-memory';

const client = new HttpClient({
  name: 'example-api',
  cache: new InMemoryCacheStore(),
  dedupe: new InMemoryDedupeStore(),
  rateLimit: new InMemoryRateLimitStore(),
  cacheTTL: 300,
});

const data = await client.get<{ name: string }>(
  'https://api.example.com/user/1',
);

Every store is optional. Use only what you need:

// Cache-only client
const client = new HttpClient({
  name: 'cached',
  cache: new InMemoryCacheStore(),
});

// Rate-limited client with no caching
const client = new HttpClient({
  name: 'rate-limited',
  rateLimit: new InMemoryRateLimitStore({
    defaultConfig: { limit: 100, windowMs: 60_000 },
  }),
});

Recommended Usage

Create a thin wrapper module per third-party API so callers don't configure anything and per-request tuning lives in one place. See the Recommended Usage guide for a full walkthrough.

API

new HttpClient(options)

HttpClient exposes a single request method: get(url, options?). The url must be an absolute URL.

Request options (client.get)

| Property | Type | Default | Description | | ---------------- | ------------------------ | -------------- | ------------------------------------------------------------------- | | signal | AbortSignal | - | Cancels wait + request when aborted | | priority | 'user' \| 'background' | 'background' | Used by adaptive rate-limit stores | | headers | Record<string, string> | - | Custom request headers (also used for Vary-based cache matching) | | retry | RetryOptions \| false | - | Per-request retry config; false disables retries for this call | | cacheTTL | number | - | Per-request cache TTL in seconds (overrides constructor) | | cacheOverrides | CacheOverrideOptions | - | Per-request cache overrides (shallow-merged with constructor-level) |

Constructor options:

| Property | Type | Default | Description | | --------------------- | ------------------------------------------ | -------- | --------------------------------------- | | name | string | required | Name for the client instance | | cache | CacheStore | - | Response caching | | dedupe | DedupeStore | - | Request deduplication | | rateLimit | RateLimitStore \| AdaptiveRateLimitStore | - | Rate limiting | | cacheTTL | number | 3600 | Cache TTL when response has no headers | | throwOnRateLimit | boolean | true | Throw when rate limited vs. wait | | maxWaitTime | number | 60000 | Max wait time (ms) before throwing | | responseTransformer | (data: unknown) => unknown | - | Transform raw response data | | responseHandler | (data: unknown) => unknown | - | Validate/process transformed data | | errorHandler | (error: unknown) => Error | - | Convert errors to domain-specific types | | cacheOverrides | CacheOverrideOptions | - | Override cache header behaviors | | retry | RetryOptions \| false | - | Retry config; false disables globally | | rateLimitHeaders | RateLimitHeaderConfig | defaults | Configure standard/custom header names |

Request Flow

  1. Cache - Return cached response if available
  2. Dedupe - If an identical request is already in-flight, wait for its result
  3. Rate Limit - Wait or throw if the rate limit is exceeded
  4. Fetch - Execute the HTTP request
  5. Transform & Validate - Apply responseTransformer then responseHandler
  6. Store - Cache the result, record the rate limit hit, and resolve any deduplicated waiters

Error Handling

All HTTP errors are wrapped in HttpClientError:

import { HttpClientError } from '@http-client-toolkit/core';

try {
  await client.get(url);
} catch (error) {
  if (error instanceof HttpClientError) {
    console.log(error.message);
    console.log(error.statusCode);
  }
}

Cancellation

Pass an AbortSignal to cancel a request, including while waiting for a rate limit window:

const controller = new AbortController();
const data = await client.get(url, { signal: controller.signal });
controller.abort();

Header-Based Rate Limiting

HttpClient respects server-provided rate-limit headers out of the box:

  • Retry-After
  • RateLimit-Remaining / RateLimit-Reset
  • X-RateLimit-Remaining / X-RateLimit-Reset

Map non-standard header names per API:

const client = new HttpClient({
  name: 'custom-api',
  rateLimitHeaders: {
    retryAfter: ['RetryAfterSeconds'],
    remaining: ['Remaining-Requests'],
    reset: ['Window-Reset-Seconds'],
  },
});

Exports

  • HttpClient - Main client class
  • HttpClientError - Error class with statusCode
  • hashRequest - Deterministic SHA-256 request hashing
  • Store interfaces: CacheStore, DedupeStore, RateLimitStore, AdaptiveRateLimitStore

License

ISC