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

@pcoi/tokens

v2.0.0

Published

PCOI Design System — design tokens (CSS custom properties + text-style utility classes).

Readme

@pcoi/tokens

Design tokens for the PCOI Design System: CSS custom properties, text-style utility classes, and the Inter / JetBrains Mono variable fonts. The CSS is hand-authored and audited against the PCOI Figma file — it is the design contract, not a codegen artifact.

Install

npm install @pcoi/tokens

Usage

Import once at your application entry:

import "@pcoi/tokens";

This loads three stylesheets:

  • fonts.css — Inter Variable and JetBrains Mono Variable (via the bundled @fontsource-variable packages)
  • tokens.css — every --* custom property (colors, spacing, radii, shadows, motion), themed via data-theme
  • typography.css — .type-* text-style utility classes

Global resets and base page styles are opt-in (they mutate global styles, so they're not loaded by default):

import "@pcoi/tokens/global.css";

Granular imports

Each stylesheet is also exported on its own subpath if you want a subset (for example, skipping the bundled fonts to self-host):

import "@pcoi/tokens/tokens.css";
import "@pcoi/tokens/typography.css";
import "@pcoi/tokens/fonts.css";
import "@pcoi/tokens/global.css";

Theming

Tokens resolve per theme through the data-theme attribute on a root element. PCOI is dark-first:

<html data-theme="dark">

Set data-theme="light" for the light mode values.

Requirements

  • A bundler that handles CSS imports (Vite, Next.js, webpack with css-loader, etc.). The JS entry point is side-effect CSS imports only, so it cannot be imported in a plain Node/SSR context without CSS handling — use the *.css subpaths directly in that case.
  • fonts.css uses bare @import "@fontsource-variable/..." specifiers, resolved by your bundler through this package's dependencies. If you self-host fonts, skip fonts.css and load your own @font-face rules.

License

MIT