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

@pearpages/pulp-tokens

v0.3.0

Published

pulp design tokens. W3C Design Tokens (DTCG) JSON in, CSS custom properties and a resolved JSON manifest out. Two brands, light and dark via light-dark().

Readme

@pearpages/pulp-tokens

The design tokens of pulp: W3C Design Tokens (DTCG) JSON in, CSS custom properties and a resolved JSON manifest out. Two brands, light and dark via light-dark().

Install

npm install @pearpages/pulp-tokens

Most apps get the tokens through @pearpages/pulp-css, which imports them in the right cascade layer. Import them directly only if you don't use it:

@import "@pearpages/pulp-tokens/tokens.css";

Use

Read the semantic names, never the primitives underneath them:

.panel {
  background: var(--color-surface-raised);
  color: var(--color-text-default);
  padding: var(--space-4);
  border-radius: var(--radius-surface);
}

Theme with two attributes on <html> or on any element (they nest):

  • data-brand="pulp" | "bitepals" sets the palette, radius, type families and density. pulp is the default on :root.
  • data-scheme="light" | "dark", or leave it off to follow the OS. Colours are light-dark() pairs.
<html data-brand="bitepals" data-scheme="dark">

Tiers

Primitives (raw palette and scales) → semantic tokens (what a value means: surface, text, action) → component tokens (one component's knobs, always pointing at semantic ones). A brand only remaps primitives onto semantic names, so switching brand never touches a component.

Files

| Export | | | --- | --- | | @pearpages/pulp-tokens/tokens.css | every brand's custom properties, in @layer tokens | | @pearpages/pulp-tokens/tokens.json | resolved tokens per brand, { pulp: [...], bitepals: [...] }; each entry has name, path, type, tier, css, value. For tooling | | @pearpages/pulp-tokens/theme.css | Tailwind v4: an @theme inline reference block over the semantic colours, radii, shadows and font families, so bg-surface-base or rounded-control read pulp's variables. Import it after tailwindcss and tokens.css | | @pearpages/pulp-tokens/native | React Native / NativeWind and Tailwind v3: per brand { colors, radius, space, themeVars: { light, dark } }. Names are var(--…) references for the config; themeVars are resolved hex and px for vars(). ESM and require | | tokens/ | the DTCG source files |

License

MIT