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

@harshilrajput/universal-api-errors-fetch

v0.1.3

Published

Fetch adapter for universal-api-errors: turns a failed Response or network error into a UniversalError.

Downloads

662

Readme

@harshilrajput/universal-api-errors-fetch

fetch adapter for universal-api-errors. Turns a failed Response or a network-level fetch rejection into a UniversalError.

Install

npm install @harshilrajput/universal-api-errors-fetch
# or: pnpm add @harshilrajput/universal-api-errors-fetch
# or: yarn add @harshilrajput/universal-api-errors-fetch

@harshilrajput/universal-api-errors-core comes along automatically as a regular dependency — no separate install needed.

Usage

fetch never throws for HTTP error statuses (404, 500, ...) — only for genuine network failures (offline, DNS, an aborted request). parseFetchError handles both cases, which is why, unlike every other parser in this ecosystem, it's async: reading a Response body requires an await.

import { parseFetchError } from '@harshilrajput/universal-api-errors-fetch';

// 1. HTTP error status
const response = await fetch('/api/user');
if (!response.ok) {
  const error = await parseFetchError(response);
  if (error.isUnauthorized) redirectToLogin();
}

// 2. Network failure / abort
try {
  await fetch('/api/user');
} catch (err) {
  const error = await parseFetchError(err);
  if (error.isOffline) showOfflineBanner();
}

Reading the response body uses response.clone(), so calling parseFetchError(response) never consumes the stream — you can still read response.json() yourself afterwards if you need the body for something else.

For the non-Response branch (network failures, AbortError), this delegates straight to the core package's parseError(), which already classifies those from the error's code/message — keeping that heuristic in one place instead of two copies drifting apart.

Everything from core, too

This package re-exports the entire @harshilrajput/universal-api-errors-core public API, so you don't need a separate import (or a separate npm install) to reach the generic surface — parseError, createUniversalError, the UniversalError class, retry, normalizeValidation, configureLogger, and every type, all from this one package:

import { parseFetchError, parseError, retry, UniversalError } from '@harshilrajput/universal-api-errors-fetch';

License

MIT