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

@plumix/admin-ui

v0.1.1

Published

Plumix admin UI primitives

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

nasyrovnasyrov

Keywords

plumixcmsuicomponents

Readme

@plumix/admin-ui

The shared shadcn/ui primitives rendered by the admin shell (@plumix/admin) and by plugin admin chunks (via plumix/admin/ui). One vendored source of truth so the shell and plugins stay visually consistent.

Adding a component

pnpm --filter @plumix/admin-ui ui:add <component>   # e.g. dialog, badge

This runs shadcn add against this package's components.json (components land flat in src/, cn imports resolve to @plumix/admin-ui) and formats the result. After adding, export it from src/index.ts and add a subpath to exports in package.json so consumers can import … from "@plumix/admin-ui/<component>".

Theme

components.json points tailwind.css at a placeholder (unused.css): the design tokens live in @plumix/admin's src/styles/globals.css, which already @sources this package so the shell CSS carries every component's classes (plugin chunks inherit them). If a newly-added component needs new CSS variables or keyframes, add them there.

Sharing with plugins

The thin wrappers ship as bundled source through plumix/admin/ui; their radix-ui / sonner / tailwind-merge imports are aliased to the host runtime shims at plugin build time, so plugin chunks reuse the shell's single radix/sonner/tailwind-merge instance instead of bundling their own.

Stability

plumix/admin/ui is a public API for third-party plugin authors, but these are vendored shadcn components we own and edit (via ui:add). It carries no guarantee beyond plumix's repo-wide policy: pre-1.0, minor versions may contain breaking changes — pin your version. A ui:add re-generation or a hand-edit to a component's markup/props counts as a breaking change under that policy, not a patch. Plugin authors should pin plumix and test their admin chunk against each minor before upgrading.

Conventions

Destructive actions. A standalone or primary destructive button (a delete button, a confirm dialog's action) uses <Button variant="destructive">. A destructive action sitting inline among non-destructive peers (a ghost action toolbar, a per-row "Remove") uses variant="ghost" plus the shared destructiveGhostClassName — never a hand-rolled text-destructive string, so the surfaces can't drift on what "destructive" looks like.