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

@tsimpl/runtime

v0.1.1

Published

Runtime trait dispatch helpers for tsimpl.

Downloads

185

Readme

@tsimpl/runtime

Traits that behave like plain JavaScript.

Use a trait once, implement it anywhere, and dispatch without ceremony. When you want runtime tagging for plain objects, plug in a Standard Schema (Zod, Joi, or your own) and tsimpl takes it from there.

POP example: Zod + trait dispatch

import { z } from "zod";
import { struct, trait, method, impl } from "@tsimpl/runtime";
import { Self } from "@tsimpl/core";

type User = { id: string; handle: string };

const UserSchema = z.object({
  id: z.string(),
  handle: z.string()
});

const UserStruct = struct(UserSchema);

const Display = trait({
  display: method<Self, string>()
});

impl(Display).for(UserStruct, {
  display: method((self) => `@${self.handle} (${self.id})`)
});

const ada = UserStruct.from({ id: "u1", handle: "ada" });
console.log(Display.display(ada));

Why it pops:

  • That value is a plain object created by Zod, not a class instance.
  • The trait impl lives alongside your domain type, not inside it.
  • Dispatch reads like normal JS: Display.display(ada).

The mental model

  1. trait(...) defines behavior.
  2. struct(...) tags plain values using Standard Schema.
  3. impl(...) wires the two together.

trait

const Display = trait({
  display: method<Self, string>()
});

Trait tokens expose static dispatch (Display.display(value)) and implement Standard Schema via the ~standard key for interoperability.

struct

const UserStruct = struct(UserSchema);

Struct tokens validate and tag values with from(...), and they can host associated statics:

import { StructSelf, associated, method, impl } from "@tsimpl/runtime";

type Self = StructSelf<typeof UserStruct>;

impl(UserStruct, {
  new: associated((id: string, handle: string) => ({ id, handle })),
  shout: method((self: Self) => self.handle.toUpperCase())
});

const tagged = UserStruct.new("u2", "grace");
console.log(UserStruct.shout(tagged));

impl

impl(Display).for(UserStruct, {
  display: method((self) => `@${self.handle} (${self.id})`)
});

Register the implementation against a struct token, a class constructor, or a plain object. Trait implementations can also use associated(...) to define static-style helpers (the self argument is ignored).

Dispatch styles

  • Static: Display.display(value).
  • Class/prototype: value.as(Display).display() (from impl(Display).for(MyClass, ...)).
  • Explicit: traitView(value, Display) or traitProxy(value, Display).
  • Symbol slot: Reflect.get(value, Display) after attachTraitSlot(...).

Colliding method names

Two traits can safely share method names because implementations are keyed per trait token. When names collide, prefer explicit dispatch (Display.display(value) or value.as(Display).display()) instead of attaching methods directly to the instance.