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

error-response-kit

v0.1.0

Published

User-friendly API error responses with clear explanations and solutions

Readme

api-error-explainer

A small Node.js / Express utility that converts HTTP status codes into user-friendly error responses with clear solutions and supports app-specific overrides.

Most APIs return errors like:

{ "error": "Not Found" }

This library helps you return responses like:

{ "status": 404, "message": "User not found", "solutions": [ "Check the user ID", "Create a new user" ], "action": "FIX_INPUT", "retryable": false }

So the client knows what to do next.

Install

npm install error-response-kit

Quick Start (Express) import express from "express"; import { attachExplainer } from "error-response-kit";

const app = express(); app.use(express.json()); app.use(attachExplainer());

app.get("/users/:id", (req, res) => { const user = null;

if (!user) { return res.explain(404, "user_not_found"); }

res.json(user); });

app.listen(3000);

Response { "status": 404, "message": "User not found", "solutions": [ "Check the user ID", "Create a new user" ], "action": "FIX_INPUT", "retryable": false }

Direct Usage (without Express) import { explainError } from "error-response-kit";

const error = explainError({ status: 404, reason: "user_not_found" });

console.log(error);

Custom Errors (Overrides)

You can add your own app-specific error explanations.

import { configureErrors } from "error-response-kit";

configureErrors({ 404: { order_not_found: { message: "Order not found", solutions: [ "Check your order ID", "Contact support if the issue persists" ], action: "FIX_INPUT", retryable: false } } });

Then use:

res.explain(404, "order_not_found");

Notes

Call configureErrors() once at app startup

This library is user-centric by design

Logging and debugging are intentionally out of scope

Safe fallbacks are used if an error is not defined

Project Status

🚧 Early version (v0.x)

This package is intentionally minimal. Feedback is welcome on:

API design

Error structure

Naming

Real-world usage

Feel free to open an issue or share suggestions.