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

@zamatica/design-tokens

v0.1.0

Published

CSS custom-property design tokens (palette, type, spacing, motion) and a Google Fonts loader helper. Zero framework deps. Override by re-declaring tokens at :root after importing.

Readme

@zamatica/design-tokens

CSS custom-property design tokens + Google Fonts loader. Zero framework deps. Drop it into any Angular / vanilla / React app.

Install

bun link @zamatica/design-tokens         # local dev (cross-repo)
# or, once published:
bun add @zamatica/design-tokens

Use

1. Import the tokens

In your app's global stylesheet (e.g. apps/<your-app>/src/styles.css):

@import '@zamatica/design-tokens/tokens.css';

Tokens become available as CSS custom properties on :root:

.my-thing {
  background: var(--bg-1);
  color: var(--fg);
  border: 1px solid var(--line-2);
  font-family: var(--mono);
  font-size: var(--fs-m);
}

2. Load the matching webfonts (one of)

Programmatic (call once at app bootstrap):

import { loadFonts } from '@zamatica/design-tokens';
loadFonts();                       // default: all three families
loadFonts({ subset: 'core' });     // skip Instrument Serif

OR static — paste the equivalent <link> tags into your index.html:

<link rel="preconnect" href="https://fonts.googleapis.com"/>
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin/>
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600&family=JetBrains+Mono:wght@400;500&family=Instrument+Serif&display=swap" rel="stylesheet"/>

The CSS file uses fallback-friendly stacks (var(--mono)"JetBrains Mono", ui-monospace, …), so missing webfonts degrade gracefully to system mono / sans / serif.

Override tokens

Re-declare any token at :root after the import. CSS cascade does the rest:

@import '@zamatica/design-tokens/tokens.css';

:root {
  --accent: oklch(0.7 0.2 250);            /* cool blue brand */
  --bg:     #0e0e10;                       /* deeper bg */
  --sans:   "Geist Sans", system-ui, sans-serif;
}

Per-theme overrides via attribute selectors:

[data-theme="light"] {
  --bg:   #FAFAF7;
  --fg:   #15151A;
  /* … */
}

Token reference

See src/tokens.css — the file is the canonical reference, grouped and commented by category (surface, foreground, accent, hue, line, status, type, fs, spacing, motion).

Status

v0.x — seed values are deliberately opinionated (warm near-black + ochre, dev-tool minimal). Descendants are expected to override. Token NAMES (e.g. --accent, --hue-warm) are the public surface; downstream code references those, not the literal color values.