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

@russfranky/shadcss-cli

v0.1.8

Published

CLI for shadcss — add components to your project, diff your copies against upstream, and lint markup. Zero dependencies.

Readme

@russfranky/shadcss-cli

The CLI for shadcss — a zero-runtime, HTML/CSS-only clone of the shadcn/ui aesthetic.

It gives you both consumption models shadcn users ask for: own the code and keep it updatable.

npx @russfranky/shadcss-cli <command>

Commands

| Command | What it does | | --- | --- | | list | List all available components | | info <component> | Show a component's classes, deps, and example markup | | add <component...> | Copy component CSS (and its deps) into your project | | diff <component> | Show how your local copy has drifted from upstream | | check <file.html ...> | Lint HTML for known a11y/markup foot-guns |

Why diff matters

shadcn's biggest complaint is "you own the code, so upstream bug/a11y fixes never reach you." With shadcss you copy components the same way — but shadcss diff <component> shows exactly what changed upstream versus your copy, so you can pull fixes deliberately instead of never noticing them.

npx @russfranky/shadcss-cli add button card dialog   # copy into ./shadcss
npx @russfranky/shadcss-cli diff button              # what changed upstream?
npx @russfranky/shadcss-cli check ./index.html       # any markup foot-guns?

Options

| Flag | Default | Description | | --- | --- | --- | | --dir <path> | ./shadcss | Target (and local-copy) directory for add / diff | | --from <dir> | — | Read from a local shadcss checkout instead of the CDN | | --version <v> | latest shipped | Framework version to pull from the CDN | | --force | false | Overwrite existing files on add |

The CLI has zero dependencies and fetches components from the jsDelivr CDN (the published @russfranky/shadcss package), so it works without installing the framework.

License

MIT