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

@domain-first/errors

v4.2.2

Published

Strongly typed namespace-based domain errors that remain identifiable across application boundaries

Readme

Define a domain error once, attach typed details, and recognize its code across API responses, queues, and services. No custom error class boilerplate. Zero runtime dependencies.

  • Typed details — autocomplete when creating errors and after narrowing with .is().
  • Namespaced codes — organize errors by domain, like USER.AUTH.INCORRECT_PASSWORD.
  • Native errors — instanceof, stack traces, and cause work as expected.
  • Ready for transport — serialize to a plain object and recognize it with .matchesCode().

Try it

npm i @domain-first/errors
import { errorNamespace } from "@domain-first/errors";

const OrderErrors = errorNamespace("ORDER");
const OutOfStock = OrderErrors.define<{ productId: string }>(
    "OUT_OF_STOCK",
);

try {
    throw new OutOfStock({ productId: "coffee-beans" });
} catch (error: unknown) {
    if (OutOfStock.is(error)) {
        // string, fully typed
        console.log(error.details.productId);
        // "ORDER.OUT_OF_STOCK"
        console.log(error.code);
    } else {
        throw error;
    }
}

Across application boundaries

JSON loses class identity. The error code survives:

const error = new OutOfStock({ productId: "coffee-beans" });
const received: unknown = JSON.parse(
    JSON.stringify(error.serialized),
);

if (OutOfStock.matchesCode(received)) {
    console.log("Offer a restock notification");
}

OrderErrors.matchesCode(received); // true for any ORDER.* error

.is() narrows runtime instances. .matchesCode() checks a code string or an object's code; it does not validate the payload or narrow its details. On an error class, it returns the class's metadata on a match, or undefined otherwise.

.serialized includes code, name, message, details, and metadata. Nested details become flat, dot-separated keys; stack and cause are omitted.

A little more when you need it

| Need | Use | | ----------------- | ----------------------------------------------------------------------------------------------------------------------------- | | Nested namespaces | OrderErrors.subnamespace("PAYMENT") → ORDER.PAYMENT.* | | Static metadata | OrderErrors.defineWithMetadata("OUT_OF_STOCK", { retryable: false }) | | Custom messages | OrderErrors.define<{ productId: string }>("OUT_OF_STOCK", { message: ({ details }) => details.productId + " is sold out" }) | | Original cause | new OutOfStock({ productId: "coffee-beans" }, { cause: originalError }) |

ESM and CommonJS supported. MIT licensed.