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

@openapi-press/error

v0.1.1

Published

The granular, HTTP-aware error system shared by every openapi-press layer.

Readme

@openapi-press/error

The granular, HTTP-aware error system shared by every openapi-press layer.

The error model

Everything an openapi-press client throws extends PressError, which splits into two families. HttpError covers responses the server actually sent: each common status gets its own class, so consumers branch with instanceof NotFoundError rather than status === 404, while code and body still carry the API's own error vocabulary. TransportError covers requests that never completed — no response, so no status.

PressError
├── HttpError                 status · code · body
│   ├── BadRequestError       400
│   ├── UnauthorizedError     401
│   ├── ForbiddenError        403
│   ├── NotFoundError         404
│   ├── ConflictError         409
│   ├── UnprocessableError    422
│   ├── RateLimitError        429
│   └── ServerError           5xx
└── TransportError
    ├── NetworkError          fetch failed
    ├── AbortError            caller cancelled
    ├── TimeoutError          time budget exceeded
    └── CircuitOpenError      refused by an open circuit breaker

Unmapped 4xx statuses resolve to plain HttpError; every 5xx resolves to ServerError with status preserved.

Usage

import {
  NotFoundError,
  RateLimitError,
  TransportError,
} from "@openapi-press/error";

try {
  const user = await client.users.get("user-123");
} catch (error) {
  if (error instanceof NotFoundError) return null;
  if (error instanceof RateLimitError) return backoff();
  if (error instanceof TransportError) return offline();
  throw error;
}

API

  • PressError — the hierarchy root: message · method · path · cause.
  • HttpError and its status subclasses — add status · code · body.
  • TransportError / NetworkError / AbortError / TimeoutError / CircuitOpenError — failures without a response.
  • errorFromResponse(method, path, response, body) — builds the status-appropriate error from a non-2xx response.
  • errorFromException(method, path, cause) — folds a thrown fetch into AbortError or NetworkError.
  • errorClassFor(status) — the class a status resolves to.
  • STATUS_ERRORS — the status → class map.