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

@acmelabs/design-system

v0.2.0

Published

The house design system as Lit web components: vercel.com/geist foundations and every Geist component at Geist's values, set in Google Sans Flex and Google Sans Code, plus the house parts.

Readme

@acmelabs/design-system

The house design system as web components. Geist foundations and every Geist component at Geist's values, set in Google Sans Flex and Google Sans Code, plus the house parts the Vercel dashboard adds. Built with Lit, one directory per element, shadow DOM with a shared global stylesheet.

Docs: https://acmelabs-15.github.io/design-system/

Use it from a CDN

No build step. Two tags:

<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Google+Sans+Flex:[email protected]&family=Google+Sans+Code:[email protected]&display=swap">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@acmelabs/[email protected]/tokens.css">
<script type="module" src="https://cdn.jsdelivr.net/npm/@acmelabs/[email protected]/dist/bundle/design-system.min.js"></script>

<acme-button variant="primary">Deploy</acme-button>
<acme-badge hue="green" subtle>Ready</acme-badge>

A host that admits a script from a CDN but no stylesheet from one (the Claude artifact CSP is one) takes the standalone bundle, which installs tokens.css into the document on import:

<script type="module" src="https://cdn.jsdelivr.net/npm/@acmelabs/[email protected]/dist/bundle/design-system.standalone.min.js"></script>

tokens.css is the global layer: the color scales, the semantic tokens, the reset, the type classes and the layout utilities. The bundle is self-contained (Lit and the labs packages are inside it) and registers every acme-* element. dashboard.css carries the page-level recipes the Vercel dashboard composes in light DOM.

Install from npm

bun add @acmelabs/design-system
import "@acmelabs/design-system"; // every element registers on import
import "@acmelabs/design-system/tokens.css";

The unbundled build under dist/ keeps Lit as a dependency, so one copy of Lit serves the whole app. Single elements import from @acmelabs/design-system/dist/components/<name>/<name>.js.

Layout

src/
  base.ts                       AcmeElement, the shared shadow reset, the icon glyphs
  index.ts                      re-exports every element
  shared/                       helpers used by several elements; element-less style families
  components/<name>/
    <name>.ts                   the element
    <name>.styles.ts            its Lit css`` module (generated from the audited sheet)
    __tests__/<name>.test.ts    bun:test with happy-dom
docs-src/                       the docs site: a Lit app on @lit-labs/router, one fragment per page
docs/                           the built site (GitHub Pages serves it)
scripts/                        split-css, build, dev server

Scripts

| Command | What it does | |---|---| | bun run build | Transpiles src/ with the Lit template compiler into dist/, then bundles dist/bundle/design-system(.min).js | | bun run docs | Builds the docs site into docs/ | | bun run dev | Rebuilds on change and serves the docs at http://localhost:4180 | | bun test | Unit tests plus a render test of every docs page | | bun run lint | Biome | | bun run split | Regenerates tokens.css and the style modules from the audited house sheet |

Release

Publishing runs in GitHub Actions through npm's Trusted Publisher (OpenID Connect), workflow publish-package.yml, environment publish-package; no npm token anywhere.

npm version patch        # bumps package.json and tags v0.1.x
git push --follow-tags   # the tag starts the publish

Conventions

  • Every element is acme-*. Properties reflect from attributes; array and object values take JSON in the attribute. Events are acme-change, acme-select, acme-toggle and so on, and they bubble and are composed.
  • Values come from vercel.com/geist. Where Geist has the component, Geist's value is the value.
  • The type families never change: Google Sans Flex for text, Google Sans Code for numbers, labels and code.
  • Labs packages in use: @lit-labs/signals (shared theme and toast state), @lit-labs/motion (collapse), @lit-labs/virtualizer (tables past a few hundred rows), @lit-labs/router (the docs app), @lit-labs/compiler (build-time template compilation). @lit-labs/testing is not used: the package does not support SSR.