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

@clef-sh/design

v0.1.10

Published

Internal Clef design tokens (Tailwind v4 @theme + TS mirror). Implementation detail of the @clef-sh/* workspaces — not a public API.

Readme

@clef-sh/design

Implementation detail — not a public API.

This package is published to npm so the @clef-sh/* workspaces (the Clef local UI, Clef Cloud) can share one set of design tokens. It is not intended for external consumption. Token names, file structure, and module shape can change in any release — including patch versions — without a deprecation cycle. If you depend on this from outside the Clef organization, expect breakage.

Single source of truth for the Clef design system. Both Clef Cloud and the Clef local UI (packages/ui) import from this package so token edits land in one place.

What's here

  • src/theme.css — Tailwind v4 @theme block. @import from any Tailwind v4 stylesheet to inherit the full color / type / radius scale.
  • src/theme.ts — TypeScript mirror of the same values. Exists for inline-style call sites that need a hex literal at runtime (legacy surfaces during migration; computed colors for SVG fills, etc.).

Usage

Tailwind v4 (preferred)

@import "tailwindcss";
@import "@clef-sh/design/theme.css";

Then use the generated utility names: bg-ink-850, text-ash-dim, border-edge, shadow-plate, etc.

TS (during migration / for dynamic colors)

import { theme, radius, shadow } from "@clef-sh/design";

const fill = theme.gold500;

What's NOT here

  • Component primitives (.clef-plate, .clef-stat, etc.) — those live in the consuming surface's own stylesheet. This package ships tokens only.
  • Icons — see lucide-react in the consuming package.

Editing tokens

Update both theme.css and theme.ts in lockstep. They mirror each other 1:1 by design; CI does not enforce parity yet (a check is on the post-migration cleanup list).