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

@jocoding-ax-partners/design-system

v4.0.0

Published

CSS-only design system built on [HeroUI v3](https://v3.heroui.com).

Readme

@jocoding-ax-partners/design-system

CSS-only design system built on HeroUI v3.

This package exports no components. You import components from @heroui/react as usual; this package ships a single stylesheet that restyles them and registers a set of design tokens. There is no provider, no wrapper, and no JavaScript.

Install

npm install @jocoding-ax-partners/design-system @heroui/react@^3 @heroui/styles@^3 tailwindcss@^4

Setup

Add one import to your Tailwind CSS entry file:

@import "tailwindcss";
@import "@jocoding-ax-partners/design-system/styles";

That is the whole setup. @jocoding-ax-partners/design-system/styles imports @heroui/styles itself, so you do not import it separately — but it stays a peer dependency and must be installed. Place the import after tailwindcss and after any stylesheet it should override.

Tailwind v4 for your framework is upstream setup — see the Tailwind installation guide. Same for HeroUI's own requirements and quick start.

import { Button } from "@heroui/react"; // ✅
import { Button } from "@jocoding-ax-partners/design-system"; // ❌ does not exist

What this package adds

data-* attributes

HeroUI's prop types cannot be extended, so the extra options ride on data attributes.

| Component | Attribute | Values | | ------------------------------- | -------------- | ----------------------------------------------- | | Button (outline, ghost) | data-color | accent danger success warning info | | ToggleButton (default, ghost) | data-color | accent danger success warning info | | Chip | data-color | info | | Checkbox.Control | data-size | md | | Checkbox.Control | data-rounded | "true" | | Radio.Control | data-size | md |

<Button variant="outline" data-color="danger">Delete</Button>

ListBox selection

Inside Select, ComboBox, Autocomplete and standalone ListBox, the item indicator is hidden and a selected item is marked by an accent background instead.

<ListBox.Item id="florida" textValue="Florida">
  Florida
  <ListBox.ItemIndicator /> {/* opts this item into the accent background */}
</ListBox.Item>

Rendering the indicator is what opts an item into that styling. An item without one keeps HeroUI's appearance, where selection is not marked at all.

Tailwind utilities

Registered on top of stock Tailwind and HeroUI:

  • Colorsaccent-50accent-950, gray-850, and an info family (info, info-soft, info-soft-foreground, …) that HeroUI does not ship
  • Radiusrounded-button-xs|sm|md|lg, rounded-input, rounded-list-box, rounded-toast, rounded-dialog, rounded-card, …
  • Spacingh-button-sm|md|lg, size-input, gap-field, …
  • Typographytext-display-0104, text-heading-0105, text-body-0103, text-caption-01|02
  • Variantlight:, the counterpart to HeroUI's dark:

Parts of HeroUI's own palette are also re-valued without adding a utility name — the gray scale is shifted to neutral oklch, and a number of semantic, surface and field roles are overridden. Keep using HeroUI's utility names for those.

Exact values live in the shipped stylesheet (node_modules/@jocoding-ax-partners/design-system/dist/styles/index.css). They are deliberately not duplicated here, because a copy drifts from the source.

Component documentation

This package does not document HeroUI's components — that is HeroUI's to maintain, and a copy here would go stale on every release. Use, in order:

  1. The HeroUI MCP server (@heroui/react-mcp) — setup
  2. v3.heroui.com/docs/react/components
  3. node_modules/@heroui/react/dist/components/<name>/<name>.d.ts — the installed version, which wins when the docs disagree with runtime behavior

Using with a coding agent

llms.txt ships inside the package and is the agent-facing reference for everything above. Point your agent at it once, e.g. in CLAUDE.md:

## @jocoding-ax-partners/design-system

This project uses @jocoding-ax-partners/design-system, a CSS-only design system on HeroUI v3.
Import all components from `@heroui/react`, never from `@jocoding-ax-partners/design-system`.
Read `node_modules/@jocoding-ax-partners/design-system/llms.txt` before writing UI code — it lists
the `data-*` extensions and design tokens this project adds on top of HeroUI.

License

MIT