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

dockyard-ui

v1.9.0

Published

Dockyard shared UI design system — design tokens and the web/ui Svelte component inventory every Dockyard surface composes.

Readme

dockyard-ui

Dockyard's shared UI design system: the design tokens and the web/ui Svelte component inventory that every Dockyard frontend surface — the inspector, the template App UIs, the docs site — composes rather than re-implementing.

This package is the only source of these building blocks (AGENTS.md §20, docs/design/CONVENTIONS.md). A page never forks a component or hard-codes a visual value; it composes the inventory and reads tokens.

What's here

  • src/tokens.css — the --dy-* design tokens as CSS custom properties (light theme; structured so a dark theme is a token-set swap).
  • src/tokens.ts — the typed token tree + the tokenVar() accessor.
  • src/*.svelte — the component inventory: shell & layout, data display, and the four-state PageState family.
  • src/index.ts — the public barrel.

Conventions

  • Plain Svelte 5, no SvelteKit (D-006). Components are framework-agnostic render units that drop into a bare iframe bundle unchanged.
  • Typed props, token-driven (no ad-hoc hex / magic spacing), keyboard-accessible with the primary focus ring.
  • Every async region routes through PageState; its empty and error panels carry real copy and a working retry — the four-state rule is mandatory.

Develop

npm install      # or: npm ci
npm run gate     # svelte-check + tsc + vitest — the frontend gate

make web runs this gate for every web/ project in CI.