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

atroui

v0.4.2

Published

AtroUI - production React / Next.js component catalog via the shadcn registry, plus optional Host API handlers. Docs at https://www.atroui.com.

Readme

atroui

AtroUI - production React / Next.js component catalog. Add components with the shadcn CLI:

npx shadcn@latest init
npx shadcn@latest add @atroui/home-hero

Docs: Installation · Registry · Host APIs

Install modes

Never lead with npm i atroui for pure UI. Use the CLI first; add the package only when /api handlers appear.

| Mode | What you get | Install | |------|--------------|---------| | Registry UI only | Heroes, chrome, form UI — owned source files | npx shadcn add @atroui/…. No atroui package. | | Forms | Contact / waitlist / newsletter UI + hardened routes | npm i atroui, transpilePackages: ["atroui"], then @atroui/contact-form + @atroui/api-contact (same for waitlist / newsletter). | | AI tools | OG, thumbnail, scope chat + matching APIs | Same package setup + @atroui/og-workspace / thumbnail-workspace / scope-chat + @atroui/api-*. |

When you still need the npm package

UI blocks copy into your repo via the CLI. Host API route handlers (atroui/api/contact, generate, thumbnail, scope, …) stay in the published atroui package so you can reuse validation, rate limits, and compose logic without vendoring native image deps.

npm i atroui
# next.config: transpilePackages: ["atroui"]
npx shadcn@latest add @atroui/api-contact

Optional shared rate limits across instances: set UPSTASH_REDIS_REST_URL + UPSTASH_REDIS_REST_TOKEN (or Vercel KV_REST_API_*). See Host APIs.

Docs

License

MIT