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

@snowyowl/tokens

v0.2.5

Published

SnowyOwl design tokens — primitives, semantic, and component-level CSS custom properties

Readme

@snowyowl/tokens

Design tokens for the SnowyOwl Design System — compiled as CSS custom properties, ES modules, and JSON.

Installation

npm install @snowyowl/tokens

Usage

CSS (recommended)

Load one theme CSS file. It sets all token variables on the appropriate selector.

<!-- Direct file path in HTML -->
<link rel="stylesheet" href="node_modules/@snowyowl/tokens/dist/css/light.css" />

Or in a CSS/JS bundler:

@import '@snowyowl/tokens/css/light';
import '@snowyowl/tokens/css/light';

Available themes

| Import path | Selector | Description | |-------------|----------|-------------| | @snowyowl/tokens/css/light | :root, [data-theme="light"] | Default light theme | | @snowyowl/tokens/css/dark | [data-theme="dark"] | Dark theme | | @snowyowl/tokens/css/light-sharp | [data-theme="light-sharp"] | Light + 0px radius | | @snowyowl/tokens/css/dark-sharp | [data-theme="dark-sharp"] | Dark + 0px radius | | @snowyowl/tokens/css/light-elevated | [data-theme="light-elevated"] | Light + stronger shadows | | @snowyowl/tokens/css/dark-elevated | [data-theme="dark-elevated"] | Dark + stronger shadows |

Switching themes at runtime

<!-- Load the base theme once -->
<link rel="stylesheet" href="node_modules/@snowyowl/tokens/css/light" />

<!-- Switch any container by setting data-theme -->
<div data-theme="dark">...</div>
<div data-theme="light-sharp">...</div>

JavaScript tokens

Each theme is also available as named ES module exports:

import { soSemanticColorInteractivePrimary } from '@snowyowl/tokens';
// → '#7c4f9e' (light theme value)

// Or import a specific theme:
import { soSemanticColorInteractivePrimary } from '@snowyowl/tokens/js/dark';

JSON

import tokens from '@snowyowl/tokens/json/light';
console.log(tokens['soSemanticColorInteractivePrimary']); // '#7c4f9e'

Token architecture

Tokens follow a three-tier hierarchy:

| Tier | Prefix | Example | Use | |------|--------|---------|-----| | Primitive | --soColor*, --soSpace*, --soRadius* | --soColorMauve600 | Raw scale values | | Semantic | --soSemantic* | --soSemanticColorInteractivePrimary | Meaning-mapped; what themes override | | Component | --soButton*, --soCheckbox* | --soButtonRadius | Per-component overrides |

Always use semantic tokens in your code, not primitives. Semantic tokens are what themes override.

Custom theming

Override only the tokens you need. CSS variables use camelCase:

[data-theme="my-brand"] {
  --soSemanticColorInteractivePrimary: #7c3aed;
  --soSemanticRadiusComponent: 0px;
  --soSemanticRadiusContainer: 4px;
  --soSemanticShadowComponent: none;
}

The four shape personality tokens control the full visual character of the system:

| Token | Controls | |-------|---------| | --soSemanticRadiusComponent | Buttons, inputs, chips | | --soSemanticRadiusContainer | Cards, panels, modals | | --soSemanticShadowComponent | Input / chip elevation | | --soSemanticShadowContainer | Card / panel elevation |

Links

License

MIT