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

@doitrix/ui

v1.5.0

Published

The Doitrix component registry — professional Vue 3 components you install into your own code with `doitrix-ui add`, built on @doitrix/headless and @doitrix/tokens.

Readme

@doitrix/ui

Professional Vue 3 components that you install into your own code. The CLI copies the source into your project, so you own it: read it, change it, keep what you use. Behaviour comes from @doitrix/headless, every value from @doitrix/tokens.

Start

bunx @doitrix/ui init              # doitrix.json, shared helpers, the icon adapter
bunx @doitrix/ui add button card data-table

Then, in your main stylesheet:

@import 'tailwindcss';
@import '@doitrix/tokens/tailwind.css';

add copies each component with everything it imports, and prints the exact packages to install, pinned to the versions this registry was built against.

Nuxt

init detects Nuxt and installs the Nuxt Icon adapter under app/ with ~ aliases. Add to nuxt.config.ts:

modules: ['@doitrix/icons/nuxt', '@nuxt/icon'],
components: [{ path: '~/components/ui', pathPrefix: false, extensions: ['.vue'] }],

extensions: ['.vue'] matters: without it Nuxt registers each component's index.ts as a component too, and icon/index.ts would shadow Nuxt Icon's <Icon>.

Components

Run bunx @doitrix/ui list for the full catalogue. By area:

  • Primitives — Stack, Text, Container, VisuallyHidden
  • Form — Button, Field (label/description/error wiring), Input, Textarea, Checkbox, Switch, RadioGroup, Select, Label
  • Display — Card (Header, Title, Description, Action, Content, Footer, Section, Grid, Field, Divider), Badge, Alert, Avatar, Separator, Skeleton, Spinner, Empty
  • Overlay — Dialog, AlertDialog, Sheet, Popover, Tooltip, DropdownMenu
  • Navigation — Tabs, Pagination
  • Data — Table parts, DataTable, TableToolbar, FacetFilter

Every component is named Doitrix* and composed from parts:

<DoitrixCard>
  <DoitrixCardHeader>
    <DoitrixCardTitle>Loan book</DoitrixCardTitle>
    <DoitrixCardDescription>Every loan across your branches.</DoitrixCardDescription>
    <DoitrixCardAction><DoitrixButton size="sm">Export</DoitrixButton></DoitrixCardAction>
  </DoitrixCardHeader>
  <DoitrixCardContent>…</DoitrixCardContent>
</DoitrixCard>

Icons

DoitrixIcon renders any Iconify icon. A bare name uses the Doitrix set (<DoitrixIcon name="check" />); a prefix uses another (name="lucide:bell"). In Nuxt it renders through Nuxt Icon; in Vue through @iconify/vue.

Staying current

Each installed file carries a stamp — the item, the registry version and a hash of what was written.

bunx @doitrix/ui diff      # current · outdated · modified · unmanaged
bunx @doitrix/ui update    # refreshes untouched files, keeps the ones you edited
bunx @doitrix/ui update --force

Removing a component

bunx @doitrix/ui remove slider

It deletes only what you name, never a component another installed one still imports, and never a file you have edited; --force removes it regardless. Shared lib/ helpers and npm packages are left in place.

Rules the components keep

  • Tokens only — no hex, no Tailwind palette colours, no numeric text sizes, no dark: overrides. Enforced by test, and every class is compiled against the real theme so a typo cannot ship.
  • Variants are closed records; one variant and one size rather than booleans.
  • asChild wherever a component might need to be a link.
  • Your class wins conflicts with the component's.