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

@mshindi-labs/refetch

v3.0.0

Published

A modern, production-grade HTTP client built on native fetch — functional TypeScript, interceptors, retry, streaming, and tree-shakeable exports

Readme

@mshindi-labs/refetch

A modern, production-grade HTTP client built on native fetch — pure functional TypeScript, interceptors, retry, streaming, and tree-shakeable exports.

Features

  • Pure functional TypeScript — no classes, no this, compose via pipe()
  • Interceptors — axios-style request/response middleware with ID-based ejection
  • Discriminated error union (RefetchError) for precise narrowing per error kind
  • Retry — per-request and instance-wide, fully configurable with custom delay/condition
  • Streaming — raw ReadableStream via stream()
  • CancellationcreateCancelToken() wraps AbortController
  • Middleware HOFswithAuth, withTimeout, withLogging, withHeaders, withBaseURL
  • Full body support — JSON, FormData, URLSearchParams, Blob, ArrayBuffer, ReadableStream
  • Full response parsing — JSON, +json variants, form-encoded, binary, text, empty bodies
  • Tree-shakeable — sub-path exports for retry, middleware, and pipe
  • Zero runtime dependencies

Installation

npm install @mshindi-labs/refetch

Quick Start

import { create } from '@mshindi-labs/refetch';

const api = create({
  baseURL: 'https://api.example.com',
  timeout: 10_000,
});

const response = await api.get<User>('/users/1');

if (response.ok) {
  console.log(response.data); // typed as User
} else {
  console.error(response.problem, response.error);
}

HTTP Methods

GET, HEAD, and DELETE take a single response generic. POST, PUT, and PATCH take two — response type and body type:

// Read
const user  = await api.get<User>('/users/1');
const users = await api.get<User[]>('/users', { page: 1, limit: 10 });

// Write — both generics explicit
const created = await api.post<User, CreateUserDto>('/users', dto);
const updated = await api.put<User, UpdateUserDto>('/users/1', data);
const patched = await api.patch<User, Partial<User>>('/users/1', { name: 'New' });

// Other
await api.delete('/users/1');
await api.head('/health');
await api.link('/images/1.jpg', {}, { headers: { Link: '<...>; rel="tag"' } });
await api.unlink('/images/1.jpg', {}, { headers: { Link: '<...>; rel="tag"' } });

// Any HTTP verb
await api.any({ method: 'PROPFIND', url: '/dav', headers: { Depth: '1' } });

Response Format

Every request returns ApiResponse<T> — the shape is identical whether the request succeeded or failed:

interface ApiResponse<T> {
  ok: boolean;              // true for 200–299
  problem: PROBLEM_CODE | null;
  originalError: Error | null;
  data?: T;
  status?: number;
  headers?: Record<string, string>;
  duration?: number;        // milliseconds
  response?: Response;      // raw fetch Response
}

// When ok === false, the error field is also present:
interface ApiErrorResponse<T> extends ApiResponse<T> {
  ok: false;
  problem: PROBLEM_CODE;
  error: RefetchError;      // discriminated union — see Error Handling
}

Type guards:

import { isOkResponse, isErrorResponse } from '@mshindi-labs/refetch';

if (isOkResponse(response)) {
  response.data; // T — guaranteed present
}

if (isErrorResponse(response)) {
  response.error; // RefetchError — fully narrowable
}

Error Handling

PROBLEM_CODE

import { PROBLEM_CODE } from '@mshindi-labs/refetch';

switch (response.problem) {
  case PROBLEM_CODE.CLIENT_ERROR:    // 400–499
  case PROBLEM_CODE.SERVER_ERROR:    // 500–599
  case PROBLEM_CODE.TIMEOUT_ERROR:
  case PROBLEM_CODE.NETWORK_ERROR:
  case PROBLEM_CODE.CONNECTION_ERROR:
  case PROBLEM_CODE.CANCEL_ERROR:
  case PROBLEM_CODE.UNKNOWN_ERROR:
}

RefetchError discriminated union

Use response.error when you need typed access to error-specific fields:

if (!response.ok) {
  switch (response.error.kind) {
    case 'http':
      console.error(response.error.status, response.error.statusText);
      break;
    case 'timeout':
      console.error(`Timed out after ${response.error.duration}ms`);
      break;
    case 'cancel':
      console.info('Cancelled:', response.error.reason);
      break;
    case 'network':
      console.error('Network failure:', response.error.cause);
      break;
    case 'parse':
      console.error('Parse error for', response.error.contentType, response.error.cause);
      break;
    case 'unknown':
      console.error(response.error.cause);
      break;
  }
}

Interceptors

Return-based, ID-tracked, and removable. Request interceptors run LIFO (last registered, first to run); response interceptors run FIFO.

// Add a request interceptor
const id = api.interceptors.request.use(
  async (config) => ({
    ...config,
    headers: {
      ...(config.headers as Record<string, string>),
      Authorization: `Bearer ${await getToken()}`,
    },
  }),
  // Optional onRejected handler
  (error) => { throw error; },
);

// Eject by ID
api.interceptors.request.eject(id);

// Response interceptor — normalize data, handle errors
api.interceptors.response.use(
  (response) => response,
  (error) => { throw error; },
);

// Clear all interceptors
api.interceptors.request.clear();
api.interceptors.response.clear();

Retry

// Instance-wide default — 3 total attempts (1 original + 2 retries)
const api = create({ baseURL: 'https://api.example.com', retry: 3 });

// Full per-request config
const response = await api.get('/data', undefined, {
  retry: {
    attempts: 4,
    delay: (attempt) => attempt * 500,            // 500ms, 1s, 1.5s
    condition: (r) => !r.ok && r.status !== 404,  // skip retry on 404
    onRetry: (attempt, last) => console.warn('Retry', attempt, last.status),
  },
});

Default condition: retry on any non-ok response except status codes 400, 401, 403, 404, 422.

Request interceptors run once before the retry loop. Response interceptors run per attempt.

Cancellation

import { createCancelToken } from '@mshindi-labs/refetch';

const { token, cancel } = createCancelToken();

// Pass the AbortSignal in config
const req = api.get('/slow-resource', undefined, { signal: token });

// Cancel from outside
cancel('User navigated away');

const response = await req;
if (!response.ok && response.error.kind === 'cancel') {
  console.log('Reason:', response.error.reason);
}

Streaming

stream() returns the raw ReadableStream without body parsing — useful for large downloads, SSE, or chunked responses:

const response = await api.stream('/large-file.bin');

if (response.ok) {
  const reader = response.data.getReader();
  while (true) {
    const { done, value } = await reader.read();
    if (done) break;
    processChunk(value); // Uint8Array
  }
}

SSE / text streams:

const response = await api.stream<string>('/events');
if (response.ok) {
  const text = response.data.pipeThrough(new TextDecoderStream());
  for await (const chunk of text) {
    console.log(chunk);
  }
}

Middleware + pipe

pipe chains middleware HOFs onto an instance without mutation at the call site:

import { create, pipe } from '@mshindi-labs/refetch';
import { withAuth, withTimeout, withLogging, withHeaders, withBaseURL } from '@mshindi-labs/refetch/middleware';

const api = pipe(
  create({ baseURL: 'https://api.example.com' }),
  withAuth(async () => await getAccessToken()),
  withTimeout(8_000),
  withLogging(),
);

| HOF | Effect | |---|---| | withAuth(getToken) | Injects Authorization: Bearer <token> per request — getToken called each time | | withTimeout(ms) | Sets request timeout for all requests | | withHeaders(headers) | Merges additional default headers | | withBaseURL(url) | Overrides the base URL | | withLogging(logger?) | Logs each request and response; defaults to console |

Sub-path import (tree-shaking):

import { withAuth, withLogging } from '@mshindi-labs/refetch/middleware';
import { pipe }                  from '@mshindi-labs/refetch/pipe';

Body Formats

All native fetch body types are passed through without transformation. Content-Type is set automatically based on body type:

| Body | Auto Content-Type | |---|---| | Plain object / array | application/json | | string | application/json | | FormData | omitted — browser sets multipart/form-data; boundary=… | | URLSearchParams | application/x-www-form-urlencoded;charset=UTF-8 | | Blob | Blob's own .type, or application/octet-stream | | ArrayBuffer / ArrayBufferView | application/octet-stream | | ReadableStream | application/octet-stream |

If you explicitly set Content-Type in your request headers, it takes precedence (except FormData, where it is always removed to preserve the browser-managed boundary).

Form-encoded body:

await api.post('/login', new URLSearchParams({ username, password }));

File upload:

const form = new FormData();
form.append('avatar', file);
await api.post('/profile/avatar', form);

Response Parsing

parseResponseBody automatically picks the right parser based on Content-Type:

| Content-Type | Parsed to | |---|---| | application/json | T via JSON.parse | | application/*+json (e.g. vnd.api+json, ld+json, problem+json) | T via JSON.parse | | application/x-www-form-urlencoded | Record<string, string> via URLSearchParams | | text/*, application/xml, application/xhtml+xml | string | | image/*, audio/*, video/* | Blob | | application/pdf, application/zip, application/gzip, Office formats, etc. | Blob | | 204 / 304 / content-length: 0 | null | | Anything else | string (fallback) |

Sub-path Exports

import { pipe }                              from '@mshindi-labs/refetch/pipe';
import { withAuth, withLogging }             from '@mshindi-labs/refetch/middleware';
import { normalizeRetryConfig, shouldRetry } from '@mshindi-labs/refetch/retry';

Dynamic Instance Configuration

api.setHeader('X-Request-Id', crypto.randomUUID());
api.setHeaders({ 'X-API-Key': 'key', 'X-Client-Version': '3.0' });
api.deleteHeader('X-Temporary');

api.setBaseURL('https://api-v2.example.com');
api.getBaseURL();

Monitors

Observe all responses after transforms — fire-and-forget (exceptions caught internally):

api.addMonitor((response) => {
  if (!response.ok) errorTracker.capture(response.error);
});

// Remove or clear
api.removeMonitor(fn);
api.clearMonitors();

TypeScript Types

import type {
  ApiResponse,
  ApiOkResponse,
  ApiErrorResponse,
  RefetchError,
  RetryConfig,
  RefetchConfig,
  RefetchInstance,
  RequestConfig,
  InterceptorManager,
  InterceptorHandler,
  Monitor,
} from '@mshindi-labs/refetch';

Deprecated: Transforms

Mutation-based transforms are still supported for backward compatibility. Prefer interceptors for new code:

// Deprecated — still works
api.addRequestTransform((config) => {
  config.headers = { ...config.headers, Authorization: `Bearer ${token}` };
});
api.addResponseTransform((response) => {
  if (response.ok) response.data = normalize(response.data);
});
api.removeRequestTransform(fn);
api.clearRequestTransforms();

// Preferred — return-based, removable by ID
const id = api.interceptors.request.use((config) => ({
  ...config,
  headers: { ...config.headers, Authorization: `Bearer ${token}` },
}));
api.interceptors.request.eject(id);

Integration with TanStack Query

import { useQuery, useMutation } from '@tanstack/react-query';

function useUser(id: string) {
  return useQuery({
    queryKey: ['user', id],
    queryFn: async () => {
      const response = await api.get<User>(`/users/${id}`);
      if (!response.ok) throw new Error(response.problem ?? 'Failed');
      return response.data;
    },
  });
}

function useCreateUser() {
  return useMutation({
    mutationFn: async (dto: CreateUserDto) => {
      const response = await api.post<User, CreateUserDto>('/users', dto);
      if (!response.ok) throw new Error(response.problem ?? 'Failed');
      return response.data;
    },
  });
}

Why Refetch?

| | refetch | axios | apisauce | |---|---|---|---| | Native fetch | ✅ | ❌ (XHR) | ❌ (wraps axios) | | Pure functional TS | ✅ | ❌ (class-based) | ❌ | | Tree-shakeable | ✅ | ❌ | ❌ (CJS only) | | Discriminated error union | ✅ | ❌ | ❌ | | Built-in retry | ✅ | ❌ | ❌ | | Built-in streaming | ✅ | limited | ❌ | | Bundle size | ~12 KB ESM | ~60 KB | ~10 KB + axios | | Runtime dependencies | 0 | 0 | axios |

Migration from v2

Interceptors replace transforms (transforms still work, but are deprecated):

// v2
api.addRequestTransform((config) => { config.headers = { ...config.headers, 'X-Key': 'v' }; });

// v3 — return-based, eject by ID
const id = api.interceptors.request.use((config) => ({
  ...config,
  headers: { ...config.headers, 'X-Key': 'v' },
}));

Body generics on POST/PUT/PATCH:

// v2
const r = await api.post<User>('/users', data);

// v3 — body type explicit
const r = await api.post<User, CreateUserDto>('/users', dto);

RetryConfig:

// v3 — per-request retry
const r = await api.get('/data', undefined, { retry: 3 });

Content-Type is no longer in default headers. It is now set automatically based on body type. Remove manual Content-Type: application/json from your instance headers — it will be set correctly for each body type automatically.

License

MIT