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

@fgrzl/fetch

v2.0.0

Published

Explicit TypeScript fetch client with typed result objects and opt-in middleware

Readme

ci

@fgrzl/fetch

An explicit TypeScript client built on native fetch, with typed ok / data / error responses and opt-in middleware.

Why It Exists

  • Requests resolve to typed result objects instead of throwing for ordinary HTTP failures.
  • The core API stays small: JSON requests, base URLs, cancellation, timeouts, and tracing headers.
  • Middleware is opt-in: add auth, retry, caching, logging, CSRF, or local rate limits only where a client needs them.
  • Importing the package creates no shared client and enables no behavior automatically.

Install

npm install @fgrzl/fetch

Quick Start

import { FetchClient } from '@fgrzl/fetch';

const api = new FetchClient({ baseUrl: 'https://api.example.com' });
const response = await api.get<{ id: number; name: string }>('/users/1');

if (response.ok) {
  console.log(response.data.name);
} else {
  console.error(response.status, response.error.message);
  console.error(response.error.body);
}

Use response.ok for control flow. Success gives you response.data; failure gives structured details in response.error.

Add Middleware

import { FetchClient } from '@fgrzl/fetch';
import { addAuthentication } from '@fgrzl/fetch/middleware/authentication';
import { addRetry } from '@fgrzl/fetch/middleware/retry';

const client = new FetchClient({ baseUrl: 'https://api.example.com' });

addAuthentication(client, {
  tokenProvider: () => localStorage.getItem('token') || '',
});

addRetry(client, {
  maxRetries: 2,
  delay: 250,
  backoff: 'exponential',
});

Each helper mutates and returns the same client. Cache, logging, CSRF, and rate limiting are available the same way when a specific client needs them.

Optional Exceptions

import { FetchClient, throwOnError } from '@fgrzl/fetch';

const api = new FetchClient({ baseUrl: 'https://api.example.com' });
const user = throwOnError(
  await api.get<{ id: number; name: string }>('/users/1'),
);

console.log(user.name);

Use throwOnError only at call sites that expect exceptions.

Documentation

Related