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

@meridui/tokens

v0.1.1

Published

Merid design tokens as W3C DTCG JSON, typed JavaScript, CSS custom properties and a Tokens Studio file for Figma, with light, dark, accent and density modes.

Readme

@meridui/tokens

The design tokens of Merid, the React component library, for code that cannot read Merid's CSS: W3C Design Tokens (DTCG) JSON, typed JavaScript, a Tokens Studio file for Figma and the source CSS. Colour, spacing, radius, type, shadow, motion, sizes and layers, with the values for every theme, accent and density.

If you use Merid's React components you already have the tokens as --mrd-* CSS custom properties through @meridui/react/styles.css. Install this package when you need the same values somewhere else: an email template, a canvas chart, a native app, a Style Dictionary pipeline or a Figma library.

npm i @meridui/tokens

JavaScript

import { cssVar, tokens } from "@meridui/tokens";

tokens.light.accent;           // "#3f63f5"
tokens.dark.accent;            // "#6b8aff"
tokens["violet-dark"].accent;  // "#9d85ff"
cssVar.space4;                 // "var(--mrd-space-4)"

tokens has one complete set of values per mode, with camelCase keys: light, dark, the accent presets (violet, green, graphite and their -dark variants), the densities (compact, comfortable), viewport-md, viewport-sm and pointer-coarse. Everything is typed.

In the browser, prefer cssVar: var(--mrd-accent) follows the active theme, a raw hex value does not. Use the raw values where CSS variables cannot reach.

Files

| Import | Contents | | :-- | :-- | | @meridui/tokens | tokens and cssVar, as above, with type declarations. | | @meridui/tokens/tokens.json | DTCG format ($value, $type), grouped as palette, color, space, radius, typography, shadow, motion, size and z. $value is resolved for the default mode (light, blue accent, default density); the other modes are under $extensions["com.merid"].modes. Each token also records its CSS variable name. | | @meridui/tokens/figma-tokens.json | Tokens Studio for Figma: a core set, sets for dark, each accent and each density, and eight themes (four accents in light and dark). | | @meridui/tokens/tokens.css | A copy of Merid's token stylesheet. |

The copied tokens.css loads the Geist fonts with ../fonts/…, which only resolves inside @meridui/react. With the React components, import @meridui/react/tokens.css instead.

Tailwind

To use Merid's colours and radii as Tailwind utilities, map the CSS variables with @theme inline; cssVar gives you the same names if you generate the theme in JavaScript. See the Tailwind guide.

Links

The tokens are generated from packages/react/styles/tokens.css in the repository, which is the single source of truth; the build fails if the light and dark blocks drift apart.

License

MIT © 2026 Ahmet Can Tiryaki