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

@butai/patterns

v0.1.0-beta.0

Published

The shared vocabulary the rest of butai is built on. It defines what a design spec looks like, the contract every theme's tokens must satisfy, and the catalog types the kits generate. If the other packages are the actors, this is the script they all read

Readme

@butai/patterns

The shared vocabulary the rest of butai is built on. It defines what a design spec looks like, the contract every theme's tokens must satisfy, and the catalog types the kits generate. If the other packages are the actors, this is the script they all read from.

What it does

Every butai kit describes its building blocks as a catalog, and every theme is a set of tokens. This package is where those shapes are defined once, so a slide kit, a theme, and a skill all agree on the same structure. It also validates that a theme fills every token the contract requires, so a theme is never half-done.

Install

pnpm add @butai/patterns

Usage

import { parseDesignSpec, validateThemeTokens, TOKEN_CONTRACT } from '@butai/patterns';

const spec = parseDesignSpec(rawYaml);
const diagnostics = validateThemeTokens(themeTokens);

A Node-only entry point is available at @butai/patterns/node for tooling that reads specs from disk.

Under the hood

  • Main exports: parseDesignSpec, TOKEN_CONTRACT, extractThemes, tokensFromSpec, validateThemeTokens, catalogVersion, and the shared types Catalog, DesignSpec, Diagnostic, PatternMeta.
  • Two entry points: . (isomorphic) and ./node (filesystem readers).
  • Source lives under src/ (spec/, tokens/, catalog/); the published tarball ships the compiled dist/.