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.0.3

Published

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

Readme

Installation

npm i @domain-first/errors

Motivation

In Domain-Driven Design, domain errors are part of the domain model, yet they are often treated as generic exceptions or untyped payloads. Serialized native Error objects lose their runtime identity after crossing process boundaries, making instanceof unusable after serialization. Domain-First Errors let you define strongly typed domain errors that remain identifiable both as runtime instances and as serialized objects.

Quick Start

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

const UserErrors = errorNamespace("USER");

const AuthErrors = UserErrors.subnamespace("AUTH");

// Define an error class
const IncorrectPasswordError = AuthErrors.define<{
    login: string;
}>("INCORRECT_PASSWORD");

// Throw and identify it
try {
    throw new IncorrectPasswordError(
        { login: "test-login" },
        // native Error.cause support
        { cause: 42 },
    );
} catch (e: unknown) {
    /**
       USER.AUTH.INCORRECT_PASSWORD: {"login":"test-login"}
       ...stack
       details: { login: 'test-login' },
       code: 'USER.AUTH.INCORRECT_PASSWORD',
       metadata: {},
       [cause]: 42
     }

     */
    console.error(e);

    // if (e instanceof IncorrectPasswordError) works as well
    if (IncorrectPasswordError.is(e)) {
        console.log(`Incorrect password (${e.details.login})`);
    }
}

// Recognize a serialized error
const error = new IncorrectPasswordError({
    login: "test-login",
});

const serializedError = JSON.parse(JSON.stringify(error.serialized));

if (IncorrectPasswordError.matchesCode(serializedError)) {
    console.log("Incorrect password");
}

About

A utility for defining strongly typed namespace-based domain errors with stable identities across application boundaries. Every defined error extends the native Error class and supports the native Error.cause property.

This makes errors easy to serialize, transport between layers, and recognize. Every error class provides two ways to identify that error type:

  • is for runtime instances (instanceof works as well);
  • matchesCode for serialized or transported errors.

Test coverage

Will be improved in upcoming versions.

| Type | Threshold | Current value | | ---------- | --------- | ------------- | | Statements | 80 % | 83.05 % | | Branches | 60 % | 64.1 % | | Functions | 85 % | 85.71 % | | Lines | 80 % | 82.14 % |