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

@216digital/ui

v0.4.1

Published

The 216digital design system: hand-written React components, design tokens and component CSS.

Readme

@216digital/ui

The 216digital design system: hand-written React components, design tokens and component CSS, extracted from the 216digital marketing site (216-mono).

Use

npm install --save-exact @216digital/ui

Peer dependencies: react and react-dom ^19.2, next >=16.3 <17 (the components use next/link).

Import each component from its own path. There is deliberately no barrel index, which would pull every client component into every import:

import { Header } from "@216digital/ui/Header";
import { cx } from "@216digital/ui/cx";

Styles

The package ships class names, not compiled Tailwind utilities. Your Tailwind build has to scan the package to generate them, and the component CSS has to load after Tailwind:

@import "tailwindcss";

/* Tailwind skips node_modules unless told otherwise. Without this line the
   page renders PARTIALLY styled, which is easy to miss. */
@source "../node_modules/@216digital/ui/dist";

/* After the Tailwind import: the package's rules sit in `@layer site`, which
   outranks Tailwind's layers only when declared after them. */
@import "@216digital/ui/styles.css";

styles.css is tokens.css plus the component CSS. @216digital/ui/tokens.css is available on its own.

The tokens alias --font-sen and --font-roboto, which you set on <html> (for example with next/font). Page-level blocks get their vertical rhythm from .page-blocks, so put that class on the element that holds them (216-mono uses its <main>).

Develop

npm install
npm run playground         # component playground at localhost:3000
npm run typecheck
npm run lint
npm run build              # tsc → dist/, CSS copied as-is
npm run check-pack         # the tarball holds only dist/ and the root docs

The playground (playground/) is a small Next app that renders the sources directly. It's dev-only and never published. See CLAUDE.md for the rules and traps, and docs/site-cutover.md for how 216-mono consumes this package.