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

cooud-ui

v0.5.0

Published

cooud-ui — add Cooud UI components to your project, shadcn-style (copy-paste registry).

Readme

cooud-ui (CLI)

Add Cooud UI components to your project, shadcn-style — you own the source.

npx cooud-ui init                 # write cooud-ui.json + lib/cn.ts + base copy deps
npx cooud-ui add button card      # copy components in (resolves dependencies)
npx cooud-ui add date-picker      # auto-pulls button, calendar, popover
npx cooud-ui list                 # list everything in the registry (alias: ls)
npx cooud-ui diff                 # show which installed components drifted

Commands & flags

| Command | Args | Flags | | ------------------ | ------------------ | --------------------------------------------------------------- | | init | — | -c, --cwd <dir> · -r, --registry <source> · -y, --yes · --skip-install | | add | [components...] | -c, --cwd <dir> · -r, --registry <source> · -o, --overwrite · --skip-install | | list (ls) | — | -c, --cwd <dir> · -r, --registry <source> | | diff | [components...] | -c, --cwd <dir> · -r, --registry <source> |

How it works

  • The registry (registry/*.json) is generated from the real @cooud-ui/ui sources by packages/cli/scripts/build-registry.ts — each item carries its source, its npm dependencies, and its registryDependencies (other components it imports), derived by parsing imports.
  • The default registry is pinned to the CLI package version (v0.2.0 here), not mutable main, so a published CLI reads the registry snapshot it was released with. Use -r, --registry ./registry when testing local registry changes before a release tag exists.
  • init installs only the base copy dependencies used by generated components (clsx, tailwind-merge, class-variance-authority, and Radix Slot). It does not install the public Cooud token and theme packages unless you add them separately for runtime theming.
  • add resolves the transitive closure of registryDependencies, writes the files into your project, and rewrites imports to your aliases: ../lib/cn.js → @/lib/cn, ./button.js → @/components/ui/button.
  • It then installs the collected npm dependencies with your package manager (bun / pnpm / yarn / npm, auto-detected).

Config (cooud-ui.json)

{
  "aliases": { "ui": "@/components/ui", "lib": "@/lib" },
  "paths": { "ui": "components/ui", "lib": "lib" },
  "registry": "https://raw.githubusercontent.com/pedrogbraz/cooud-ui/v0.2.0/registry"
}

Point -r, --registry <path-or-url> at a local registry/ directory for offline use or testing. Regenerate the registry after changing components: bun run -F cooud-ui registry. Verify it is in sync locally with bun run -F cooud-ui registry:check.