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

@xue160709/omni-ui-shadcn

v0.1.0

Published

shadcn registry source for OmniUI components and recipes.

Readme

@xue160709/omni-ui-shadcn

Optional shadcn registry source for OmniUI.

Use @xue160709/omni-ui-react directly when you are adding multimodal behavior to an existing React app. Use this registry when you want editable shadcn-style wrappers and starter recipes installed into your project.

The registry installs source files into components/multimodal/*. It does not replace or overwrite your existing components/ui/*.

Install Registry Items

Install one or more published registry items with the shadcn CLI:

npx shadcn@latest add https://xue160709.github.io/omni-ui/r/multimodal-provider.json
npx shadcn@latest add https://xue160709.github.io/omni-ui/r/multimodal-button.json
npx shadcn@latest add https://xue160709.github.io/omni-ui/r/multimodal-assistant-panel.json

During local development of this monorepo, start the demo-todo app first:

npm run dev

Then install one or more registry items with the shadcn CLI:

npx shadcn@latest add http://127.0.0.1:5173/r/multimodal-provider.json
npx shadcn@latest add http://127.0.0.1:5173/r/multimodal-button.json
npx shadcn@latest add http://127.0.0.1:5173/r/multimodal-assistant-panel.json

What It Installs

Low-level wrappers:

| Category | Registry items | | --- | --- | | Buttons and toggles | button, button-group, toggle, toggle-group | | Text inputs | input, textarea, input-otp, input-group | | Choice controls | checkbox, radio-group, switch, select, native-select, combobox | | Navigation | tabs, breadcrumb, navigation-menu, menubar, pagination, sidebar | | Overlays | dialog, alert-dialog, sheet, drawer, popover, tooltip, hover-card, context-menu, dropdown-menu | | Data and layout | table, list-item, card, item, scroll-area, resizable, progress | | Feedback and content | alert, empty, toast, sonner, calendar, date-picker, carousel | | Command surfaces | command |

Starter recipes:

  • multimodal-assistant-panel: chat/command panel with local actions before optional model fallback.
  • multimodal-form: semantic form, section, and action groups.
  • multimodal-data-table: data view with visible-order row semantics and row action buttons.

Styling

Installed files are local source code. You can edit class names, markup, behavior, and theme usage directly.

The registry intentionally relies on the consumer app's shadcn components, Tailwind setup, and CSS variables instead of shipping a separate design system.

Registry source recipes import OmniUI base styles with:

import "@xue160709/omni-ui-react/styles.css"

Maintainer Commands

Generate local registry JSON for preview:

npm run registry:build

The generated files are written to apps/demo-todo/public/r and public/r.

Run registry tests and rebuild the registry output:

npm run verify:registry