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

stepwise-ui

v0.1.2

Published

Add Stepwise UI components to your project

Readme

stepwise-ui

CLI for Stepwise UI - copies component source into your project so you own it outright. No runtime package, no version lock, no wrapper around someone else's abstraction.

npx stepwise-ui init

Using this from a coding agent

An agent arriving here first should read llms.txt - the whole library in one request, every component with its exports and a usage example, so you can pick a real component instead of writing one from scratch.

Then use add, not init: init is an interactive picker and needs a TTY. add never touches project config, so it is safe to run unattended. The Agents guide has the details, including a drop-in AGENTS.md block.

Commands

init

Browse the registry and install what you pick, in one step. Search by name, select what you want, and the source is written into your project.

npx stepwise-ui init

It also offers to set up the two things components need but cannot do for themselves - the dark-mode variant and the @/ path alias - and asks before touching either file.

Needs a real terminal, since it is an interactive picker. In a script, CI or an agent session use add instead, and list --all to see what is available.

add <components...>

Copies one or more components into your project, follows their dependencies, and installs any npm packages they need.

npx stepwise-ui add button                 # one component
npx stepwise-ui add button input select    # several at once
npx stepwise-ui add date-picker            # pulls in `calendar` automatically
npx stepwise-ui add button --yes           # overwrite files you've edited

Files land at the paths the component declares - components/stepwise/… for the components themselves, lib/utils/cn.ts for the shared class helper.

A file that already exists and matches is left alone. A file you've since edited is not overwritten unless you pass --yes, so local changes survive a re-run.

list (alias ls)

The Stepwise components already in this project, grouped by category. Add --all for the full registry instead.

npx stepwise-ui list          # what this project already has
npx stepwise-ui list --all    # every component available

Requirements

  • Node 18+

  • React 19

  • Tailwind CSS v4

  • An @/* path alias pointing at your project root:

    // tsconfig.json
    { "compilerOptions": { "paths": { "@/*": ["./*"] } } }

    Components import each other through this alias. The CLI warns if it's missing.

  • A class-based dark variant in your global stylesheet:

    @custom-variant dark (&:where(.dark, .dark *));

    Dark mode is class-based, not prefers-color-scheme. Without this line every dark: class in every component silently does nothing - it is the single most common way a Stepwise install looks broken. init offers to add it; add warns when it is missing.

No component imports from next/*, so none of this is tied to Next.js - it works in Vite, Remix, or plain React. The CLI tells you when a component needs a package your project doesn't have, and installs it. React itself is the exception: that is a framework-level choice, so it is reported and left to you.

Pointing at a different registry

STEPWISE_REGISTRY_URL=http://localhost:3000/r npx stepwise-ui add button

Useful when working on the registry itself.

License

MIT