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

@directorkit/ui

v0.1.1

Published

Component kit and design tokens for Nuxt — auto-registered <D*> components on reka-ui, with the palette living in the UnoCSS theme.

Readme

@directorkit/ui

The component kit and the design tokens: auto-registered <D*> components built on reka-ui for behaviour and UnoCSS for styling, plus @nuxtjs/color-mode and nuxt-lucide-icons riding along with the layer.

Install

npm install @directorkit/ui
// nuxt.config.ts
export default defineNuxtConfig({
  extends: ["@directorkit/ui"],
});
// uno.config.ts — REQUIRED, see below
export { default } from "@directorkit/ui/uno.config";

@directorkit/ui is a Nuxt layer, not a built library: it ships raw .vue source and the consuming app's Vite compiles it. nuxt and vue are peer dependencies.

Why the uno.config.ts re-export is mandatory

The palette is the UnoCSS theme, and a Nuxt layer cannot ship a Uno config transitively — @unocss/nuxt only discovers a config at the app root. Every consumer therefore re-exports ours from its own uno.config.ts. Skip this step and the components render unstyled. (The modules themselves — Uno, color-mode, lucide — do come with the layer; you declare none of them.)

Components

Auto-registered with the D prefix, flat (pathPrefix: false):

<DBadge> <DButton> <DButtonGroup> <DCard> <DChip> <DDateField> <DDatePicker> <DEmpty> <DFormField> <DInput> <DInputNumber> <DKbd> <DPinInput> <DSelect> <DSkeleton> <DSwitch> <DTimeField> <DToggle> <DToggleGroup> <DToggleGroupItem>

<template>
  <DCard>
    <DFormField label="Name">
      <DInput v-model="name" placeholder="Ada Lovelace" />
    </DFormField>
    <DButton variant="primary" @click="save">Save</DButton>
  </DCard>
</template>

Each component is four files — .vue, .types.ts, .variants.ts and .spec.ts — so the variant matrix (built with class-variance-authority) is readable and overridable on its own. Icons come from nuxt-lucide-icons with the Icon prefix (<IconCheck />).

To bind these inputs to a form model instead of a plain v-model, add @directorkit/form-ui.

Documentation

Design-token and component-authoring decisions are recorded in the repo's ADRs — 0005 (one component, four files), 0006 (reka-ui and context), 0007 (the palette).

License

MIT © Tomáš Petržela