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

@teamblind-chorus/tokens

v4.1.0

Published

Chorus design tokens — three-tier source (reference / system / component), dereferenced `resolved.*.json` bundles, and a ready-to-import `tokens.css` that emits every token as a CSS custom property. Regenerate with `npm run build:tokens`.

Readme

@teamblind-chorus/tokens

🇰🇷 한국어: i18n/ko/schema/tokens/README.md

Design tokens for Chorus. Ships three-tier source JSON (reference → system → component), dereferenced resolved.*.json bundles for non-CSS consumers, and tokens.css emitting every token as a CSS custom property.

Token meaning lives in schema/DESIGN.md. This package ships values only.

License: MIT. See LICENSE.

Install

For full setup (stylesheet imports, dark mode, native ports, upgrading), see @teamblind-chorus/ui's README — this token package is normally installed transitively via @teamblind-chorus/ui.

npm install @teamblind-chorus/tokens

CSS bundle (most common)

import '@teamblind-chorus/tokens/tokens.css';

Emits:

  • :root { … } — every token as --ref-* / --sys-* / --comp-* (light theme).
  • [data-theme="light"] { … } — same set, so a subtree can flip back to light.
  • [data-theme="dark"] { … } — dark-mode overrides only (diff vs. light).
  • @media (min-width: 800px) { … } — web-breakpoint overrides (typo sizes only; spacing is flat across the mobile↔web line).

Toggle dark mode: data-theme="dark" on <html> or any ancestor.

.button {
  background: var(--sys-color-background-accent-blue);
  color: var(--sys-color-text-onFill);
  padding: var(--sys-space-md);
  border-radius: var(--sys-radius-md);
}

Font-size is rem (base 1rem = 16px) so text honors the user's browser / OS font-size preference. For that to work, don't hard-set the root font-size to a px value — html { font-size: 16px } pins the root and silently disables the user's preference; leave <html> at the browser default (or font-size: 100%). Spacing, radius, and other dimensions stay px; native ports read the px values, not rem.

JSON bundles (AI agents, design tools, native renderers)

import light from '@teamblind-chorus/tokens/resolved.light.json';
import dark  from '@teamblind-chorus/tokens/resolved.dark.json';

Each entry: { "<dotted.path>": { "$value": …, "$type": … } }, fully dereferenced. Web-breakpoint overrides in sparse resolved.web.json / resolved.web.dark.json.

Three-tier source (advanced)

import reference from '@teamblind-chorus/tokens/reference.json';
import system    from '@teamblind-chorus/tokens/system.json';
import component from '@teamblind-chorus/tokens/component.json';

Values may be DTCG-style references ("{ref.palette.blue.500}"); resolve yourself. Use only if you need source structure (e.g. retheme by swapping the reference tier).

Rebuilding

From repo root:

npm run build:tokens

Regenerates every resolved.*.json and tokens.css. Source of truth: the three .json files in this directory.