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/types

v5.0.2

Published

Type-safe domain models powered by Standard Schema validation

Readme

Installation

npm i @domain-first/types

Motivation

Domain models often need both runtime validation and domain-specific behavior. Keeping validation, type inference, and business logic together can lead to repetitive boilerplate.

Domain-First Types creates type-safe domain models from Standard Schema validators while leaving domain-specific behavior to your classes.

Features

  • Runtime validation through any Standard Schema compatible library
  • Full TypeScript inference
  • Domain behavior through class methods
  • Recursive domain types

Examples

Quick Start

import { domainType } from "@domain-first/types";
// any schema library supporting Standard Schema can be used
import { z } from "zod";

class UserId extends domainType(z.string().nonempty()) {
    static get randomId() {
        return new UserId(globalThis.crypto.randomUUID());
    }
}

class User extends domainType(
    z.object({
        id: z.instanceof(UserId),
        name: z.string().nonempty(),
    }),
) {
    withNewName = (name: string) => {
        return new User({
            id: this.id,
            name,
        });
    };
}

const user = new User({
    id: UserId.randomId,
    name: "First User",
});

console.log(user.name); // 'First User'
// user.name = 'New Name' -> TS Error

/**
 * Domain types created from primitive schemas
 * expose their value through the `value` property.
 */
console.log(user.id.value); // 'user-1'
// user.id.value = 'new value' -> TS Error

console.log(user.withNewName("Test Name").name); // 'Test Name'

Recursive types

import z from "zod";
import { recursiveDomainType } from "@domain-first/types";

class Node extends recursiveDomainType((isNode) => {
    return z.object({
        id: z.string().nonempty(),
        linkedNode: z.custom<Node>(isNode).optional(),
    });
}) {}

const node = new Node({ id: "1" });
const nodeWithLink = new Node({ id: "2", linkedNode: node });

console.log(nodeWithLink.linkedNode?.id); // 1

Error handling

import { domainType, TypeParsingError } from "@domain-first/types";
import z from "zod";

class NonEmptyString extends domainType(z.string().nonempty()) {}

try {
    const _string = new NonEmptyString("");
} catch (e: unknown) {
    if (e instanceof TypeParsingError) {
        console.error(e.details.parsingIssues);
        console.error(e.details.value);
    }
}