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

ui8kit

v2.0.1

Published

CLI to install and maintain UI8Kit component/block registries (multi-runtime, file-based)

Readme

ui8kit CLI v2

Universal shadcn-style registry service: init / add / list / diff / scan / build — fetch registry items and write files into your app (not into node_modules). Tailwind sees classes. Works for React, Svelte, Vue, Solid, Go Templ, Latte/Twig — via framework / runtime + path contracts.

Contract version: 2.0.0

Full documentation (English): docs/README.md

| Start here | | |------------|--| | Getting started | Install + first init/add | | Commands | Complete CLI reference | | Scenarios | React, Svelte, Templ, private CDN, publish, CI | | Registry format | Item / index JSON contract |

Idea

registry (CDN / digest)  →  npx ui8kit add  →  {dir}/components/ui/...
                                            →  {dir}/utils, lib, blocks, layouts, …

Codegen (separate) emits primitives; this CLI installs registry packages into app folders and can scan/build local registry artifacts for publishing.

Requirements

  • Node.js >=20 (or Bun)
  • A project with package.json (created by init if missing)
  • No hard requirement for Vite/React

Quick start

bunx ui8kit@latest init --yes --framework svelte --dir web/src
bunx ui8kit@latest add button --runtime svelte

Go / PHP apps (kit on disk for Tailwind / templ):

bunx ui8kit init --yes --framework templ --dir internal --skip-core
bunx ui8kit add button --runtime templ --registry-url https://example.com/r

Canonical folders under {dir}

| Path | Role | Registry type | |------|------|----------------| | lib/ | low-level runtime helpers | registry:lib | | utils/ | shared helpers (cn, …) | registry:utils | | components/ | composites | registry:component / composite | | components/ui/ | primitives (codegen digest) | registry:ui | | blocks/ | page sections | registry:block | | layouts/ | chrome / shells | registry:layout | | variants/ | variant maps | registry:variants | | widgets/ | UI + behavior | registry:widget |

Remap without breaking the contract:

{
  "dir": "web/src",
  "paths": { "ui": "kit", "utils": "kit/utils" }
}

Config (ui8kit.config.json)

{
  "contractVersion": "2.0.0",
  "framework": "svelte",
  "runtime": "svelte",
  "typescript": true,
  "globalCss": "web/src/app.css",
  "dir": "web/src",
  "aliases": {
    "@": "./web/src",
    "@/ui": "./web/src/components/ui",
    "@/utils": "./web/src/utils"
  },
  "registry": "@ui8kit",
  "registryUrl": "https://cdn.example.com/ui8kit/r",
  "registryVersion": "0.1.0",
  "cdnBaseUrls": [
    "https://cdn.example.com/ui8kit/r"
  ],
  "strictCdn": true,
  "importStyle": "alias"
}

CDN resolution order

  1. --registry-url / registryUrl
  2. cdnBaseUrls from config (replaces built-in defaults when set)
  3. Built-in defaults (unpkg / jsdelivr / GitHub raw)

--strict-cdn + explicit URL → only that URL.

--registry-version rewrites @latest@0.1.0 in URL templates.

Commands

init

bunx ui8kit init
bunx ui8kit init --yes --framework none --dir src
bunx ui8kit init --yes --framework templ --dir internal --skip-core
bunx ui8kit init --registry-url https://my-cdn/r --strict-cdn

Creates ui8kit.config.json + canonical directories. Optionally pulls lib/utils/variants from registry.

add

bunx ui8kit add button
bunx ui8kit add button card --force
bunx ui8kit add --all --runtime svelte
bunx ui8kit add button --dry-run
bunx ui8kit add button --registry-url https://my-cdn/r --registry-version 0.1.0

Install preserves nested paths (e.g. components/ui/button/Button.svelte), no basename flatten.

Runtime filter: when --runtime or config.runtime is set, only that stack’s files are written, plus shared brick assets (*.shared.ts, *.variants.json). Utils/lib items are installed in full. Items that declare a different item-level runtime field are skipped entirely.

# Multi-file brick on CDN → only Svelte + shared land on disk
bunx ui8kit add button --runtime svelte

list / diff / info / cache / reset / scan / build

Same roles as v1; info --cdn shows resolved CDN order.

Registry item (contract)

{
  "name": "button",
  "type": "registry:ui",
  "runtime": "svelte",
  "digest": "0.1.0",
  "dependencies": ["clsx", "tailwind-merge"],
  "registryDependencies": ["utils"],
  "files": [
    {
      "path": "ui/button/Button.svelte",
      "target": "components/ui/button/Button.svelte",
      "content": "..."
    },
    {
      "path": "ui/button/button.variants.json",
      "target": "components/ui/button/button.variants.json",
      "content": "..."
    }
  ]
}

Breaking changes (v1 → v2)

  • framework: "vite-react"react | svelte | … | none
  • init no longer requires Vite + React
  • Install paths use {dir}/… + optional paths remap
  • File install preserves relative structure (target / path), not basename-only
  • New types: registry:utils, registry:widget
  • Config fields: dir, runtime, cdnBaseUrls, contractVersion

Registry publish loop

  1. Author/kit digest published as registry JSON on a CDN base
  2. Apps: ui8kit init + ui8kit add --runtime … --registry-version D
  3. Maintainers: ui8kit scanui8kit build to assemble packages/registry/r
  4. Tailwind content / @source points at {dir}/**

Development / publish

npm install
npm run type-check
npm test
npm run build
npm run pack:check   # dry-run tarball contents
# npm publish        # after npm login; runs prepublishOnly

Maintainer scripts (local fixtures, CDN probe): see scripts/README.md.

User & author guides: see docs/README.md.

License

MIT