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

@simple-base/tokens

v0.2.5

Published

Design tokens and color themes for Simple Base, as CSS custom properties and JavaScript.

Readme

@simple-base/tokens

Design tokens for Simple Base: primitives, semantic roles, and nine color themes, generated with Terrazzo.

Every token is emitted as a CSS custom property named --sb-<token-path>, and the full set is also available as JavaScript objects for tooling.

Install

pnpm add @simple-base/tokens

Quick start

Load the token stylesheet once, before component or application styles:

@import "@simple-base/tokens/css";

Then use the custom properties anywhere:

.panel {
  background: var(--sb-semantic-color-background-surface);
  color: var(--sb-semantic-color-foreground-primary);
  border: 1px solid var(--sb-semantic-color-border-default);
  border-radius: var(--sb-semantic-radius-md);
}

Theming

simple-base-dark is the default and applies to :root. Every other theme activates through data-theme, on the document root or any nested element:

<html data-theme="nord"></html>

| Theme | Color scheme | | ---------------------- | ------------ | | simple-base-dark | dark | | simple-base-light | light | | catppuccin-latte | light | | catppuccin-frappe | dark | | catppuccin-macchiato | dark | | catppuccin-mocha | dark | | dracula | dark | | tokyo-night | dark | | nord | dark |

Each theme is a scoped selector, so different regions of a page can use different themes. The matching color-scheme is set alongside the variables.

Theme contract

Every theme layers its surfaces the same way — canvas for the page, surface for cards and fields, then raised and overlay as one small step up each — and meets these contrast minimums against the surface and canvas it sits on:

| Role | Minimum | | ---------------------------------------------------------- | ------- | | foreground.primary, secondary, muted text | 4.5:1 | | accent.text and status.*.text, also on *.soft | 4.5:1 | | accent.on-surface, status.danger.on-surface | 4.5:1 | | border.strong (field, checkbox, switch outlines) | 3:1 | | status.danger.base (invalid borders) | 3:1 | | status.*.base on *.soft (glyphs), when text is colored | 3:1 | | focus.ring, accent.surface | 3:1 |

Two roles meet no minimum, so keep them off text and control boundaries:

  • foreground.subtle falls below 4.5:1 in catppuccin-latte. Use muted for de-emphasized text.
  • border.default falls below 3:1 in every theme. It is for dividers and card edges; field and control outlines use border.strong.

Ported palettes

Catppuccin, Dracula, Tokyo Night, and Nord use only their official palette colors. Each theme file declares its palette under $extensions["org.simple-base.theme"].palette, and each color token names the palette color it uses in $extensions["org.simple-base.palette"]. Colors are never lightened or darkened to pass contrast. Instead, each role picks a palette color that passes, and the only adjustment is the opacity of tints and the modal scrim.

Each status color is shown one of three ways, whichever its palette allows:

  • Tinted: the label in the status color on a tint of the same color. Most statuses in the dark palettes.
  • Shaded: the label in the status color on the palette's darkest color, where a tint would lower its contrast too far. Frappé and Dracula danger.
  • Body text: the label in the body color, with the status color on the glyph, tint, and border. Used where no palette pairing reaches 4.5:1: every status in Latte, and Nord danger and info.

Some palettes also need a different layering. Latte and Nord use the same color for canvas and surface, because their accent or field-border color only reaches contrast on the lightest (Latte) or darkest (Nord) background; cards are set apart by their border. Dracula and Tokyo Night use their comment grays only for borders, and set secondary and muted text in their lighter text colors. Frappé sets muted text in subtext1, like secondary, because subtext0 falls below 4.5:1 on raised.

The one exception is Nord's danger-surface, the danger button fill: no Nord color reaches 4.5:1 as text on nord11, so it uses nord11 darkened. The exception is recorded in the token.

Tailwind CSS

For Tailwind CSS v4, use the generated theme instead of importing the token stylesheet directly. It imports Tailwind and the tokens, and maps the semantic roles onto Tailwind theme variables:

@import "@simple-base/tokens/tailwind";
<div class="bg-background-surface text-foreground-primary rounded-md">…</div>

Tailwind must be installed in the consuming project. Utilities resolve the same semantic CSS variables as the component styles, so they follow data-theme too. Each theme also gets a @custom-variant for conditional utilities:

<div class="nord:bg-background-raised">…</div>

Breakpoints are generated as literal dimensions, because CSS media queries cannot resolve custom properties.

JavaScript and TypeScript

The package root exposes the token resolver and full token types:

import { resolver, type Tokens } from "@simple-base/tokens";

const tokens: Tokens = resolver.apply({ theme: "dracula" });

tokens["semantic.color.foreground.primary"].$value;

| Export | Description | | ----------------------------- | -------------------------------------------------------------------------------- | | resolver.apply() | Resolves a permutation (for example { theme: "nord" }) and returns its tokens. | | resolver.listPermutations() | Lists every available permutation. | | PERMUTATIONS | All permutations keyed by their serialized input. | | Tokens | Type of a resolved token set; individual value types are exported too. |

Reference

Variable naming. Dots in a token path become hyphens: semantic.color.foreground.primary becomes --sb-semantic-color-foreground-primary.

Primitives versus semantic roles. Primitive tokens such as --sb-primitive-color-accent are raw values. Semantic tokens name a purpose and are the stable public surface — prefer them in application and component styles, since a theme changes semantics rather than primitives.

Versioning

Simple Base is on 0.x. All its packages go to 1.0.0 together, once @simple-base/react ships the same components as @simple-base/solid. Until then a minor release can include breaking changes.

Links

License

MIT