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

@campminder/ds

v0.5.0

Published

Campminder design system components, packaged. base-ui-era shadcn primitives + domain components + design tokens, for apps that prefer npm install over shadcn copy-source.

Downloads

1,098

Readme

@campminder/ds

The Campminder design system as an npm package — base-ui-era components + design tokens, for apps that prefer npm install over shadcn copy-source. The package is generated from the registry (npm run sync), so it never drifts from what the design system ships.

Published to the public npm registry (no auth). Requires React 19 · Next.js App Router · Tailwind v4.

Install

npm install @campminder/ds @base-ui/react

@base-ui/react is a peer (you control its version); everything else the components need is pulled in automatically.

Wire up styles — one line

/* your globals.css, after Tailwind */
@import "tailwindcss";
@import "@campminder/ds/styles.css";   /* tokens + the @source Tailwind needs */

That single import gives you the Campminder tokens (so bg-primary is brand purple) and the Tailwind scanning of the package's components. No config file.

Use

import { Button, Card, Badge, PhoneInput, CamperForm } from "@campminder/ds"

Works in Server Components — the package carries its own client boundary.

What's included

  • Primitives: avatar, badge, breadcrumb, button, card, checkbox, command, dialog, field, input, input-group, label, popover, scroll-area, select, separator, sheet, sidebar, skeleton, switch, table, tabs, textarea, tooltip
  • Domain components: phone-input, photo-upload, step-card, step-notices, session-card / session-picker, person-list, person-tabs, camper-form, package-picker, addon-picker
  • Hooks / utils: use-locale, use-mobile, session-selection helpers, cn

Not yet included: the admin shell (sidebar/search/top-nav) — deferred to a follow-up. Pull those from the copy-source registry for now.

Versioning

semver, shared with the registry's registry-versions.json. npm update @campminder/ds to take changes; nothing updates under you.

Maintaining (for the design system team)

src/ is generated from the registry by scripts/sync-from-registry.mjs (runs automatically in npm run build). Don't hand-edit src/ — edit the source components in the design system, and the package mirrors them. styles.css is likewise generated from app/globals.css.

npm run build      # sync from registry → generate tokens → bundle (ESM+CJS+dts)