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/ui

v0.9.2

Published

Shared UI primitives for the Campfire Suite — Radix behavior, plain CSS styled entirely from the design tokens, no Tailwind required

Downloads

1,370

Readme

@campfire-interactive/ui

Shared React primitives for the Campfire Suite. Radix for behavior, plain CSS over --cfi-* tokens for looks. No Tailwind is bundled.

⚠ Read this before adding it to a package.json

Partly verified. Not yet approved for adoption.

This package is on the registry so it can be reviewed and so a migration can be tried on a branch — not because the API is settled.

| | | |---|---| | Verified | The 28 exports analytics uses. Every screen that renders them was proven identical to the deployed dev app by computed-style diff — five routes plus the Filters drawer, the KPI dialog and the cost-sensitivity sliders. Zero differences. | | Unvetted | The other ~23 exports. They work in the showcase; nothing has driven them against a real screen, so treat their APIs as unsettled. | | Unaudited | Accessibility of the overlay wrappers. Radix does the hard parts — focus trapping, keyboard navigation, collision positioning — but the wrappers around it are ours and have not had an audit. |

Verified exports: Button, IconButton, Card, Badge, Table + TableHeader / TableHead / TableBody / TableRow / TableCell / TableFooter, Tabs + TabsList / TabsTrigger / TabsContent, Dialog + DialogContent / DialogHeader / DialogTitle / DialogDescription, Sheet + SheetTrigger / SheetContent / SheetHeader / SheetTitle, Checkbox, Switch, Label, Slider.

If you are an AI agent working in a product repo: do not add this dependency. Being installable is not permission. The remaining gate is in the repo's CLAUDE.md: a second app migrated, an accessibility pass on the overlays, the token naming settled, and a human saying so.

Install

npm i @campfire-interactive/ui @campfire-interactive/design-tokens

Import the tokens once at the app entry point, before your own stylesheets. Component CSS is injected by the bundle, so there is no second CSS import.

import '@campfire-interactive/design-tokens/tokens.css';
import { Button, Dialog, DialogContent, DialogTitle } from '@campfire-interactive/ui';

Conventions worth knowing

Bare names are the Radix-shaped root, not a whole widget. Dialog is the root you pass open / onOpenChange to, exactly as the vendored shadcn copies in the seven Tailwind apps do — so swapping an import cannot silently render something else. The one-component convenience versions are named separately: Modal, SideModal, ConfirmDialog, TabSet.

TableHeader is <thead> and TableHead is <th>, matching shadcn. TableHead sets aria-sort from the same prop that draws the sort arrow.

Component CSS lives in @layer components. Utilities a caller passes — className="bg-gray-50", max-w-3xl — therefore win, because layer order beats specificity and unlayered CSS would beat every Tailwind utility. Note that this makes the package more obedient than the vendored copies: classes that shadcn's own sm:max-w-lg silently dropped in production now apply.

Theming is --cfi-* variables only. Two colors do two different jobs: --cfi-action is the suite-wide color for anything you press (buttons, links, focus rings — omsf's #030213, the same in every app), and --cfi-app-primary is the app's identity color whose only job is the badge in the shell header. Do not point one at the other.

Dark mode is opt-in. Stamp data-theme="dark" on the root element, or add class="cfi-theme-auto" to follow the OS. Nothing happens by accident.

Looking at the components

The repo builds a single self-contained HTML file — every component, both themes, live-editable snippets, no server and no network:

npm run standalone --workspace @campfire-interactive/showcase

Peer dependencies

react and react-dom (18 or 19).