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

@dustin-riley/design

v0.5.0

Published

Dustin Riley design system — warm mid-century modern tokens and primitives.

Readme

@dustin-riley/design

Warm mid-century-modern design system: tokens, base resets, and a curated set of reusable CSS primitives. Framework-neutral, with an optional Tailwind v4 + shadcn bridge.

Install

npm i @dustin-riley/design

Use

/* any project */
@import "@dustin-riley/design/tokens.css";
@import "@dustin-riley/design/core.css";

/* Tailwind v4 + shadcn projects also need: */
@import "@dustin-riley/design/tailwind.css"; /* pulls in core + tokens */

That's the whole contract. No separate reset, no @layer, nothing per-app.

What's in / out

tokens.css--ds-* custom properties + the focus ring. Pure tokens, no element styling.

core.css — generic primitives (.ds-btn*, .ds-container, .ds-panel, typographic helpers, .kbd, …) plus minimal base element styling (body defaults, heading font/size, mono code, ::selection). Imports tokens.css. Base rules are wrapped in :where() (zero specificity) so any app/component/ Preflight rule wins.

Links are not underlined by default. Per DESIGN.md, links are color-only; the system never sets a global link text-decoration. Underline is an intentional, component-scoped decision (e.g. article body) made by the app.

tailwind.css — optional Tailwind v4 @theme + shadcn HSL bridge (pulls in core + tokens). Does not include reset.css.

Out by design: site furniture (nav, footer, hero, content grids). Build those per project from the tokens. See DESIGN.md.

Maintaining the bridge

src/tailwind.css is generated. Never edit it by hand. After changing src/tokens.css, run npm run generate && npm test.