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

@mich8060/unified-design-system

v0.2.7

Published

This repo is a working reference implementation showing:

Readme

UDS Sample Application (Spec-driven + SCSS + Multi-brand + Governed App Shell)

This repo is a working reference implementation showing:

  • Token-driven SCSS architecture (primitives → semantics → brands)
  • Design-system components styled with SCSS (BEM, no raw values)
  • Spec-driven component contracts (spec objects in code)
  • Canonical component template + spec template
  • A governed, configurable application shell with routing (routing lives in the shell)
  • Brand + theme applied at the shell root
  • Slot-based shell regions + structured layout config
  • Linting “lockdown” (ESLint + Stylelint) and a CLI scaffold generator

Quick start

npm install
npm run dev

Scripts

  • npm run dev – start Vite dev server
  • npm run build – production build
  • npm run preview – preview build
  • npm run lint – eslint
  • npm run lint:styles – stylelint for scss
  • npm run format – prettier
  • npm run generate:component -- Name – scaffold a new component folder from the canonical template

See /docs for the full methodology and governance model.

  • Claude Rules – conventions and constraints for AI-assisted development in this repo

NPM package quick start

Install the package and required peer dependencies:

npm i @mich8060/unified-design-system react react-dom react-router-dom @phosphor-icons/react

Import components and styles:

import { AppShell, Button, Flex, Menu, Text, TextInput } from "@mich8060/unified-design-system";
import "@mich8060/unified-design-system/styles.css";

Common prop pitfalls

  • Button uses appearance, not variant
    • valid values: primary, soft, outline, text, ghost, disabled, destructive
  • Text requires a variant value such as heading-32 or body-16
  • TextInput icon placement uses iconPosition with left or right
  • Menu mode uses light or dark

Exported constants

Use exported constants to avoid guessing valid values:

import {
  BUTTON_APPEARANCES,
  TEXT_VARIANTS,
  TEXT_WEIGHTS,
  TEXT_INPUT_STATES,
  ICON_APPEARANCES
} from "@mich8060/unified-design-system";