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

@codelitdev/design-system

v0.4.1

Published

Shared CodeLit design tokens, Tailwind preset, and React primitives for CourseLit, MediaLit, SendLit, and FrontLit.

Readme

@codelitdev/design-system

Shared tokens, Tailwind preset, and React primitives for CourseLit, MediaLit, SendLit, and FrontLit.

The tokens + Tailwind preset are the product; the React components are reference/fallback (see step 5). Consuming apps typically use only the CSS and the preset and keep their own shadcn components.

Install

Published to npm as a public package. The current release line is a prerelease under the alpha dist-tag.

[!WARNING] latest currently also points at 0.1.0-alpha.0. npm always sets latest on a package's first-ever publish, regardless of --tag — this is unavoidable until a real stable version is cut, at which point publishing it moves latest forward automatically. Until then, always pin the exact version — do not bun add @codelitdev/design-system bare, and do not use a caret/tilde range (^0.1.0-alpha.0 would still resolve to a prerelease, which is at least explicit — but a bare install with no version silently means "whatever latest is," which right now is this alpha).

bun add @codelitdev/[email protected]

Platform examples consume the package as workspace:*. Product repositories consume an exact published version.

Use in a shadcn app

  1. Import the token layer once, e.g. in app/globals.css:
@import "@codelitdev/design-system/styles.css";

This replaces the default shadcn :root/.dark block — variable names match, so existing shadcn components need no code changes.

  1. Extend your Tailwind config:
// tailwind.config.js
const codelitPreset = require("@codelitdev/design-system/tailwind-preset");
module.exports = {
  presets: [codelitPreset],
  content: [...],
};
  1. Scope the product on the <html> element (not <body>):
<html data-product="sendlit">  {/* courselit | medialit | sendlit | frontlit, omit for CodeLit amber */}

[!IMPORTANT] Put data-product on <html>, not <body>. The product scope only overrides --primary/--ring; any token you alias at :root that references --primary (e.g. shadcn's --sidebar-primary: var(--primary)) resolves that var() at the declaring element. If the override sits on <body> (a child of :root), those :root aliases freeze to the base amber and never pick up the product accent — while direct bg-primary utilities still turn green, producing a confusing split.

  1. Fonts: load Hanken Grotesk + Spline Sans Mono via next/font/google (or your framework's font loader), mapped to --font-sans / --font-mono.

  2. Components — install from the shadcn registry (see Components below). These are real shadcn/Radix components styled to the design system, so your app's buttons/badges/cards are the DS's — no hand-porting. The plain-React src/components/ classes (components.css) remain as visual reference only.

  3. Logos: @codelitdev/design-system/assets/logo-<product>.svg.

  4. Loaders — a drawn-from-the-logo spinner, not a static asset:

import { Loader } from "@codelitdev/design-system";
<Loader product="sendlit" size={32} />

Renders in currentColor, same as an icon component — wrap it (or an ancestor) in whatever sets the color you want, e.g. className="text-primary" for the product accent.

Components (shadcn registry)

The design system ships its components as a shadcn registry so every product installs the same styled components (buttons, badges, cards, …) via the shadcn CLI — keeping all four apps on one component layer instead of each re-styling its own. They're standard shadcn/Radix components; they pull their look from the DS tokens, so make sure @codelitdev/design-system/styles.css is imported (above).

Add the registry namespace to your app's components.json:

{
  "registries": {
    "@codelit": "https://raw.githubusercontent.com/codelitdev/platform/main/packages/design-system/public/r/{name}.json"
  }
}

Then install components like any other shadcn component:

bunx shadcn@latest add @codelit/button @codelit/badge @codelit/card

Or install a single component directly by URL, no config:

bunx shadcn@latest add https://raw.githubusercontent.com/codelitdev/platform/main/packages/design-system/public/r/button.json

Available components

| Component | Notes | |---|---| | button | primary / secondary / outline / ghost / soft / destructive; sm md lg (30/36/42px) | | icon-button | Square icon-only; ghost / outline; sm md | | badge | default / neutral / success / warning / destructive / outline; dot prop | | card | + CardHeader CardTitle CardDescription CardContent CardFooter | | input | Accent-wash focus ring; aria-invalid → destructive | | textarea | Multiline form of input | | label | 13px semibold field label | | checkbox | 18px, 5px radius, accent fill when checked | | radio-group | + RadioGroupItem | | switch | 36×21 track, accent when on | | select | Trigger matches input; token-styled popover | | tabs | Segmented; active trigger lifts onto a card surface | | dialog | Warm scrim, 16px radius; full Radix parts | | dropdown-menu | Matches select's popover treatment; full Radix parts incl. checkbox/radio items and submenus | | tooltip | Dark chip; TooltipProvider included | | toast | Presentational card (default/success/destructive) — drive with your own queue |

Install everything at once:

bunx shadcn@latest add @codelit/button @codelit/icon-button @codelit/badge @codelit/card \
  @codelit/input @codelit/textarea @codelit/label @codelit/checkbox @codelit/radio-group \
  @codelit/switch @codelit/select @codelit/tabs @codelit/dialog @codelit/dropdown-menu \
  @codelit/tooltip @codelit/toast

Maintainers: component sources live in registry/codelit/ui/. After changing one, rebuild the served JSON with bun run registry:build (→ public/r/*.json) and commit it — the raw-URL install serves those committed files.

Publishing

Prereleases go under the alpha dist-tag so a plain bun add never grabs one. Releases are driven from the Platform root through Changesets; do not run bun publish from this package directory:

bun run changeset
bun run release:alpha

Verify: bun info @codelitdev/design-system --json should show the prerelease under alpha and leave latest untouched.

License

Apache-2.0 — see LICENSE.