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

@optizon/tokens

v0.4.0

Published

Theme tokens and Tailwind CSS integration for Optzn UI.

Readme

@optizon/tokens

Apache-2.0 semantic design tokens for Optzn UI 0.4.0. Requires Tailwind CSS 4 (4.1.14 or later; ^4.1 installs the newest 4.x release). Keep @tailwindcss/vite on the same version as tailwindcss: its Vite peer range decides which Vite works (Vite 8 needs 4.2.2 or later).

npm install @optizon/[email protected] @optizon/[email protected]
npm install -D tailwindcss@^4.1 @tailwindcss/vite@^4.1

Configure a Tailwind 4 build integration, then load this in your application CSS:

@import "@optizon/tokens";
@source "../node_modules/@optizon/ui/src";

Adjust the source path relative to your stylesheet and import the stylesheet once from your app entry point. The token stylesheet includes Tailwind. Use UIProvider from @optizon/ui for light, dark, and system themes.

Chart palette

The stylesheet also defines the data-visualization palette @optizon/charts draws with, for light and dark themes, available as CSS variables and Tailwind colors (--color-ui-chart-*):

  • --ui-chart-1 … --ui-chart-8: categorical series colors in a fixed order. Series take them in order of first appearance, never hashed or cycled. Each clears 3:1 contrast on the chart surfaces of both themes.
  • --ui-chart-sequential-1 … -7: one blue hue for magnitude; 1 is the smallest value (closest to the surface), 7 the largest. The ramp flips on the dark theme so larger values stay more prominent.
  • --ui-chart-diverging-negative-3 … -1, --ui-chart-diverging-neutral, --ui-chart-diverging-positive-1 … -3: orange below and blue above a midpoint, with a stone neutral.

Status tokens (--ui-success, --ui-danger, --ui-warning, --ui-info) use emerald, rose, amber and sky. Fills are lighter in light mode and darker in dark mode; text-ui-success-text, text-ui-danger-text, text-ui-warning-text and text-ui-info-text use separate --ui-<status>-text tokens for readable text. Text on solid danger and info fills uses --ui-danger-foreground and --ui-info-foreground. Status colors are not series colors. The full table, values and contrast notes are in docs/TOKENS.md at https://github.com/optzn/ui.