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

@qfetch/middleware-response-error

v0.1.0

Published

Fetch middleware for throwing errors based on HTTP response status codes.

Readme

@qfetch/middleware-response-error

Fetch middleware for throwing errors on HTTP error responses.

Overview

Automatically throws errors for HTTP responses based on status codes. By default, throws a ResponseError for any response with status >= 400. Provides flexible customization through status-specific mappers and configurable thresholds, enabling standardized error handling across your application.

Intended for use with @qfetch/core.

Installation

npm install @qfetch/middleware-response-error

Quick Start

import { withResponseError, ResponseError } from '@qfetch/middleware-response-error';
import { withRetryStatus } from '@qfetch/middleware-retry-status';
import { withBaseUrl } from '@qfetch/middleware-base-url';
import { upto, zero } from '@proventuslabs/retry-strategies';
import { compose } from '@qfetch/core';

// Custom application errors
class NotFoundError extends Error {
  constructor(public url: string) {
    super(`Resource not found: ${url}`);
    this.name = 'NotFoundError';
  }
}

// API client with custom error handling
const api = compose(
  withResponseError({
    statusMap: new Map([
      [404, (res) => new NotFoundError(res.url)],
      [400, async (res) => {
        const body = await res.json();
        return new Error(`Validation failed: ${body.message}`);
      }],
    ]),
  }),
  withRetryStatus({ strategy: () => upto(3, zero()) }),
  withBaseUrl('https://api.example.com/v1/'),
)(fetch);

try {
  const user = await api('users/123').then(r => r.json());
} catch (error) {
  if (error instanceof NotFoundError) {
    // Handle 404 specifically
  } else if (error instanceof ResponseError) {
    // Handle other HTTP errors (500, etc.)
    console.log(error.status, error.statusText);
  }
}

Documentation

For complete API reference, examples, and type definitions, see the API documentation.

Standards References