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

@campfire-interactive/design-tokens

v0.4.0

Published

Shared design tokens for Campfire Suite — raw scales, semantic roles, per-app accent hooks, and an opt-in dark theme

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

priyacfipriyacfiluke-campfireluke-campfirekarthi37karthi37udaybandaruudaybandarugeorgeb-campfiregeorgeb-campfiresusithasusitha

Keywords

Readme

@campfire-interactive/design-tokens

The source of truth for every shared value in the Campfire Suite — colors, type, spacing, radii, shadows, motion, z-index, chart series and chrome dimensions — as CSS custom properties under a --cfi- prefix.

tokens.css is the source; tokens.json is generated from it by scripts/generate.mjs and resolves the var(--cfi-app-*, fallback) chains to literals for non-CSS consumers.

⚠ 0.2.x is a rewrite, and adoption is not open yet

0.1.1 had 42 tokens. 0.2.0 has 148, in three layers, with an opt-in dark theme. The semantic naming is not settled until more than one app has migrated onto it, so treat these names as movable.

One name already moved: the orange ramp is --cfi-color-orange-*, renamed from --cfi-color-primary-*. Raw scales in this file are named by hue, so a role word in a palette slot read as "the primary color" — which is how buttons ended up wired to it. It is master-data's and pim's app-identity color. The color of anything you press is --cfi-action.

Three published packages still reference the old name with literal fallbacks (shell-header, side-nav, volume-intelligence-ui), and that is deliberate: with the token gone they keep rendering their own literals, which is exactly what they render today. No alias is provided, because an alias would resolve volume-intelligence-ui's blue buttons to orange the moment an app imports this file.

^0.1.1 does not resolve to 0.2.0 — a caret below 1.0 never crosses a minor — so nothing picks this up by accident. Bumping to ^0.2.0 is a deliberate act, and the gate for it is in the repo's CLAUDE.md.

Install

npm i @campfire-interactive/design-tokens
// once, at the app entry point, BEFORE the app's own stylesheets
import '@campfire-interactive/design-tokens/tokens.css';

Declaring the dependency does nothing on its own. It was a dependency of eleven frontends and imported by none of them; the --cfi-* variables reached those pages only because shell-header and side-nav bundle their own use of them. Import the stylesheet, or the tokens are not there.

The three layers, and which one to reference

  1. Raw scales — --cfi-color-gray-500, --cfi-font-size-sm. Palette values. Reference these only when defining a semantic token.
  2. Semantic roles — --cfi-surface, --cfi-content-muted, --cfi-border, --cfi-action, the focus ring, the overlay. This is what component CSS should use. A component that reaches past these into a raw gray cannot be re-themed and breaks in dark mode.
  3. App overrides — --cfi-app-primary and friends. The app's own identity color, for the shell badge. Set these in the consuming app.

Two colors, two jobs

--cfi-action is the suite-wide color for anything you press — buttons, links, focus rings, selected rows. Its value is omsf's #030213, because omsf is the reference for main styles. It is identical in every app; that is the point of it.

--cfi-app-primary is the app's identity color, and its only job is the app badge in the shell header plus its tile in the app switcher. The canonical value per app is the color field in shell-header's appCatalog.

Do not point one at the other. Wiring buttons to the app color makes the same primary button violet in one app, sky blue in another and indigo in a third — the opposite of a design system.

Dark mode is opt-in

<html data-theme="dark">          <!-- explicit -->
<html class="cfi-theme-auto">     <!-- follow the OS -->

Neither happens by accident, so adding this file to an app that has never considered dark mode cannot change how it looks today.

Status colors

Each semantic hue carries a -soft background and a -text foreground that meets 4.5:1 against it. Use the pair. bg-[#10B981]/10 text-[#10B981] — the shape several apps had — lands near 2:1.