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

hzero

v0.1.47

Published

A themed React component layer. Ships an opinionated theme and an ergonomic API.

Readme

hzero

A themed React component layer. Opinionated about looks, comfortable to build against.

The test for whether something belongs here: would a second project want it? isOpen/onClose — yes. size="medium" — yes. A status called "checked out" meaning danger — no, that is one app's world and it stays in that app.

Install

npm install hzero
import "hzero/styles.css"
import { Button, Card, Select } from "hzero"

That one stylesheet is everything — an app that doesn't use Tailwind needs nothing else. Components are hz-* CSS. Preflight is deliberately excluded; a component library has no business resetting its host's base styles.

If your app also uses Tailwind, add this

@import "tailwindcss";
@source "../node_modules/hzero/dist/*.js";

Not for the classes — they already ship — but for ordering. Tailwind only guarantees that md: and lg: variants sort after their unprefixed counterparts within one compilation. Across two, that breaks: StatCards renders grid-cols-2 lg:grid-cols-7, and if your app generates grid-cols-2 too, yours wins from the higher layer and the grid never leaves two columns.

Scanning dist puts both classes in your compilation, where Tailwind orders them correctly. Note it is dist, not src — only dist is published, and the class strings survive in the bundled JS. A @source pointing at src matches nothing and fails silently.

React 18+ is a peer dependency. If you link hzero from a checkout rather than the registry, add resolve.dedupe: ["react", "react-dom"] to your Vite config — a symlinked package resolves its own React copy and every hook throws Invalid hook call.

The site

npm run dev
  • Home — install, the npm package, and why the layer exists
  • Components — every export, live, with a light/dark split

Each sample is isolated, so one broken component reports its error instead of taking the page down. npm run site:build writes the static site to site-dist/.

Scripts

| | | | --- | --- | | npm run dev | the package site | | npm run site:build | static site — site-dist/ | | npm run site:test | mount every site page | | npm run build | library — dist/index.js, dist/styles.css |

build:css concatenates the theme ahead of the component sheets, so dist/styles.css is standalone. It is a build artifact, never edited by hand.