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

throw-me

v1.0.7

Published

HTTP error factory for Node.js

Readme

throw-me

A lightweight, semantic, and TypeScript-first HTTP error factory.

Installation

npm install throw-me

Available Errors

| Method | Status | Description | | -------------------------- | ------------ | --------------------------------- | | Throw.badRequest() | 400 | Invalid or malformed request. | | Throw.validation() | 400 | Input validation failures. | | Throw.unauthorized() | 401 | Authentication is required. | | Throw.forbidden() | 403 | Authenticated but not permitted. | | Throw.notFound() | 404 | Resource does not exist. | | Throw.conflict() | 409 | Resource already exists/conflict. | | Throw.internal() | 500 | Generic server failure. | | Throw.notImplemented() | 501 | Feature not yet implemented. | | Throw.serviceUnavailable() | 503 | Server is down or overloaded. | | Throw.custom(msg, code) | User defined | Throw any specific status code. |

Example

import express, { Request, Response } from "express";
import { ThrowMe as Throw, BaseError } from "throw-me";

const app = express();

app.get("/user/:id", (req: Request, res: Response) => {
  const userId = req.params.id as string;
  try {
    if (!userId) {
      throw Throw.badRequest("Missing User ID");
    }

    if (userId !== "1") {
      throw Throw.unauthorized("Access Denied");
    }
    res.send("success");
  } catch (error: any) {
    if (error instanceof BaseError) {
      // Handles 400, 401, 404, etc. automatically
      res.status(error.statusCode).send(error.message);
    } else {
      // Fallback for unexpected bugs
      res.status(500).send("unexpected error!");
    }
  }
});

Extending the Error Library

If the built-in methods in ThrowMe aren't enough, you can easily create custom errors that maintain compatibility with the BaseError system and TypeScript's type-checking.

import { BaseError, ThrowMe } from "your-library-name";

// 1. Define your custom error class
class CustomPaymentError extends BaseError {
  public recoveryStep: string;

  constructor(message: string = "Payment required", recoveryStep: string) {
    super(message, 402); // 402 Payment Required
    this.recoveryStep = recoveryStep;
  }
}

// 2. Use it in your logic
function processOrder() {
  throw new CustomPaymentError(
    "Subscription expired",
    "Visit /billing to renew",
  );
}

// 3. Catch with full Type Safety
try {
  processOrder();
} catch (error) {
  if (error instanceof CustomPaymentError) {
    // TypeScript knows 'recoveryStep' exists here!
    console.error(`Error: ${error.message}. Action: ${error.recoveryStep}`);
  }
}