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

@hoardodile/ui

v0.1.15

Published

shadcn/ui component library for hoardodile plugin iframes.

Readme

@hoardodile/ui

The design-system component library for hoardodile — the host app and plugin iframes alike. Import components per-path so bundles stay small; hooks live under @hoardodile/ui/hooks/* and shared CSS variables in @hoardodile/ui/theme.css.

Install

pnpm add @hoardodile/ui

CSS toolchain

The theme stylesheet (@hoardodile/ui/theme.css) is Tailwind v4 CSS with @import statements left for your build to resolve. Consuming it requires the Tailwind toolchain in your own project:

pnpm add -D tailwindcss tw-animate-css shadcn

tailwindcss (plus your Tailwind plugin, e.g. @tailwindcss/vite), tw-animate-css and shadcn are declared as optional peer dependencies so package managers surface them; install them alongside @hoardodile/ui and import the theme from your entry stylesheet:

@import "@hoardodile/ui/theme.css";

The theme stylesheet carries a @source glob that points at the package's compiled component outputs, so your Tailwind picks up the component classes automatically — no @source configuration on your side. (This contract is enforced by the scan-contract test in the package.)

Import paths

| Entry | Contents | | ----- | -------- | | @hoardodile/ui/components/* | Components, one module each (button, dialog, dropdown-menu, popover, app-dialog, dropdown-select, icon, surface, form, …) | | @hoardodile/ui/icons/* | The icon domain: registry (every Solar glyph, wrapped), marks (✓/×/+), actions (action-to-glyph vocabulary), icon-style | | @hoardodile/ui/hooks/* | Hooks (use-mobile, useMobileBackToClose, use-form-field, use-dialog-footer-actions, …) | | @hoardodile/ui/lib/* | Utilities (cn, …) | | @hoardodile/ui/theme.css | Theme CSS: .light / .dark variables and per-palette .theme-<id> blocks | | @hoardodile/ui/viewport | Shared mobile viewport constants (MOBILE_BREAKPOINT_PX, MOBILE_QUERY, …) | | @hoardodile/ui | App-owned root pieces: AppDialog, cn, navigation resolver |

Example

import { Button } from "@hoardodile/ui/components/button"
import { AppDialog } from "@hoardodile/ui"

export function Picker({ open, onClose }) {
	return (
		<AppDialog open={open} onOpenChange={onClose} title="Pick">
			<Button onClick={onClose}>Done</Button>
		</AppDialog>
	)
}

Theming

@hoardodile/ui/theme.css defines the design tokens both the host app and plugin iframes consume. The plugin iframe applies the host theme via applyTheme from @hoardodile/sdk-web — palette classes like theme-parchment are defined here.