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

@marianmeres/http-utils

v2.5.1

Published

[![NPM version](https://img.shields.io/npm/v/@marianmeres/http-utils)](https://www.npmjs.com/package/@marianmeres/http-utils) [![JSR version](https://jsr.io/badges/@marianmeres/http-utils)](https://jsr.io/@marianmeres/http-utils) [![License: MIT](https://

Readme

@marianmeres/http-utils

NPM version JSR version License: MIT

Opinionated, lightweight HTTP client wrapper for fetch with type-safe errors and convenient defaults.

Features

  • 🎯 Type-safe HTTP errors - Well-known status codes map to specific error classes
  • 🔧 Convenient defaults - Auto JSON parsing, Bearer tokens, base URLs
  • 🪶 Lightweight - Zero dependencies, thin wrapper over native fetch
  • 🎨 Flexible error handling - Three-tier error message extraction (local → factory → global)
  • 📦 Deno & Node.js - Works in both runtimes
  • 🦾 Generic return types - Optional type parameters for typed responses

Installation

deno add jsr:@marianmeres/http-utils
npm install @marianmeres/http-utils
import { createHttpApi, opts, HTTP_ERROR } from "@marianmeres/http-utils";

Quick Start

import { createHttpApi, opts, HTTP_ERROR, NotFound } from "@marianmeres/http-utils";

// Create an API client with base URL
const api = createHttpApi("https://api.example.com", {
  headers: { "Authorization": "Bearer your-token" }
});

// GET request (options API with opts() wrapper)
const users = await api.get("/users", opts({
  params: { headers: { "X-Custom": "value" } }
}));

// POST request (options API with opts() wrapper)
const newUser = await api.post("/users", opts({
  data: { name: "John Doe" },
  params: { headers: { "X-Custom": "value" } }
}));

// Legacy API (default behavior without opts())
const legacyUsers = await api.get("/users", { headers: { "X-Custom": "value" } });
const legacyUser = await api.post("/users", { name: "John Doe" });

// With type parameters for typed responses
interface User { id: number; name: string; }
const user = await api.get<User>("/users/1");
const created = await api.post<User>("/users", opts({ data: { name: "Jane" } }));

// Error handling
try {
  await api.get("/not-found");
} catch (error) {
  if (error instanceof NotFound) {
    console.log("Resource not found");
  }
  // or use the namespace
  if (error instanceof HTTP_ERROR.NotFound) {
    console.log(error.status); // 404
    console.log(error.body);   // Response body
  }
}

API Overview

createHttpApi(base?, defaults?, errorExtractor?)

Creates an HTTP API client.

const api = createHttpApi("https://api.example.com", {
  headers: { "Authorization": "Bearer token" }
});

HTTP Methods

// GET (options API with opts() wrapper)
const data = await api.get("/users", opts({
  params: { headers: { "X-Custom": "value" } },
  respHeaders: {}
}));

// POST/PUT/PATCH/DELETE (options API with opts() wrapper)
await api.post("/users", opts({
  data: { name: "John" },
  params: { token: "bearer-token" }
}));

// Legacy API (default behavior without opts())
const data = await api.get("/users", { headers: { "X-Custom": "value" } });
await api.post("/users", { name: "John" });

The opts() Helper

The opts() function explicitly marks an options object for the options-based API. Without it, arguments are treated as legacy positional parameters.

// Without opts() - legacy behavior: object is sent as request body
await api.post("/users", { data: { name: "John" } });  // Sends: { data: { name: "John" } }

// With opts() - options API: data is extracted and sent as body
await api.post("/users", opts({ data: { name: "John" } }));  // Sends: { name: "John" }

This makes the API unambiguous and prevents accidental misinterpretation of request data.

Error Handling

import { HTTP_ERROR, NotFound } from "@marianmeres/http-utils";

try {
  await api.get("/resource");
} catch (error) {
  if (error instanceof NotFound) {
    console.log("Not found:", error.body);
  }
  // All errors have: status, statusText, body, cause
}

Key Features

  • Auto JSON: Response bodies are automatically parsed as JSON
  • Bearer tokens: Use token param to auto-add Authorization: Bearer header
  • Response headers: Pass respHeaders: {} to capture response headers
  • Raw response: Use raw: true to get the raw Response object
  • Non-throwing: Use assert: false to prevent throwing on errors
  • AbortController: Pass signal for request cancellation
  • Typed responses: Use generics for type-safe responses: api.get<User>("/users/1")

Full API Reference

For complete API documentation including all error classes, HTTP status codes, types, and utilities, see API.md.

Utilities

getErrorMessage(error)

Extracts human-readable messages from any error format:

import { getErrorMessage } from "@marianmeres/http-utils";

try {
  await api.get("/fail");
} catch (error) {
  console.log(getErrorMessage(error)); // "Not Found"
}

createHttpError(code, message?, body?, cause?)

Manually create HTTP errors:

import { createHttpError } from "@marianmeres/http-utils";

const error = createHttpError(404, "User not found", { userId: 123 });
throw error; // instanceof NotFound