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

@lootvm/registry-docs

v0.1.1

Published

LootVM UI — component usage docs for docs site and MCP

Readme

@lootvm/registry-docs

Structured component and block usage documentation for the LootVM UI ecosystem.

This package exports usage data — import snippets, JSX examples, and block templates — consumed by the docs site and baked into the lootvm-ui CLI registry at build time.

Note: Most users should install lootvm-ui (CLI) or @lootvm/ui (component library) instead of this package directly.

Installation

npm install @lootvm/registry-docs

Exports

import {
  COMPONENT_DOCS,
  BLOCK_USAGE,
  getComponentDoc,
  formatImportBlock,
  formatNpmImportBlock,
} from "@lootvm/registry-docs";

| Export | Type | Description | |--------|------|-------------| | COMPONENT_DOCS | Record<string, ComponentDoc> | Usage data for all 46 components | | BLOCK_USAGE | Record<string, BlockDoc> | Usage data for 5 page blocks | | getComponentDoc | (slug: string) => ComponentDoc \| undefined | Lookup a single component | | formatImportBlock | (slug: string) => string | Format CLI-style import snippet | | formatNpmImportBlock | (slug: string) => string | Format npm-style import snippet |

Data shape

type ComponentDoc = {
  imports: string[];  // exported symbol names
  usage: string;      // JSX example
};

Consumers

| Consumer | How it uses this package | |----------|--------------------------| | Docs site (lootvm-ui-internal) | Renders component showcases and usage examples | | lootvm-ui CLI | Prebuild script serializes docs into docs.json and blocks-docs.json for MCP tools |

The CLI build pipeline (scripts/build-cli-registry.ts) reads from this package and embeds the data into the published lootvm-ui tarball — so MCP users get usage examples without installing this package separately.

Contributing

To add or update component documentation:

  1. Edit src/component-docs.ts for components or src/block-docs.ts for blocks
  2. Rebuild: pnpm build (from the monorepo root or this package)
  3. Rebuild the CLI registry: pnpm prebuild --filter=lootvm-ui

Each entry should include the exported symbol names and a minimal working JSX example.

Links

License

MIT