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

@ambient-ui/docs

v0.1.13

Published

The system's account of itself — the component catalog, the governing documents, and the built registry index, shipped as a versioned package so the site (or any consumer) renders the release it depends on.

Readme

@ambient-ui/docs

The ambientui system's account of itself, as a versioned package.

Two things ship here:

  • The component catalog (@ambient-ui/docs/catalog): what every documented component is, in serializable prose. Summary, behaviour, when to use, when not to. No React, no imports; a Node script can read it as easily as a page can render it.
  • Content snapshots (@ambient-ui/docs/content/*): the governing documents (DESIGN.md, the specs, the Figma contract) and the registry index, copied from the repository at build time, so a consumer renders the release it depends on rather than whatever the repo's HEAD says.

This is how the ambientui website stays honest across repositories: it imports this package, and its build fails if its demos fall out of step with the catalog a new release ships.

npm i @ambient-ui/docs
import { AMBIENT_COMPONENTS, SHADCN_DEFAULT_COMPONENTS } from "@ambient-ui/docs"

You probably only need this package if you are building tooling or documentation around ambientui. The human-readable reference is at ambientui.ai/ds.

MIT (c) Lumenridge