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

@muskanmeet/invoicing-design-system

v0.1.2

Published

Invoicing UI design system — tokens, Tailwind preset and shadcn-based React components.

Readme

@yourteam/invoicing-ui

Design system powering the Invoicing app — design tokens, a Tailwind preset, and shadcn-based React components on top of Radix primitives.

Install

npm install @yourteam/invoicing-ui
# peer deps
npm install react react-dom tailwindcss tailwindcss-animate

Usage

1. Import the CSS once

In your app entry (e.g. app/layout.tsx, pages/_app.tsx, main.tsx):

import "@yourteam/invoicing-ui/styles.css";

styles.css includes @tailwind base/components/utilities plus the token CSS variables. If you already manage your own Tailwind entry, import just the tokens instead:

@import "@yourteam/invoicing-ui/tokens.css";

2. Extend the Tailwind preset

// tailwind.config.ts
import type { Config } from "tailwindcss";
import preset from "@yourteam/invoicing-ui/tailwind-preset";

export default {
  presets: [preset],
  content: [
    "./app/**/*.{ts,tsx}",
    "./src/**/*.{ts,tsx}",
    // include the package so its class names survive purging
    "./node_modules/@yourteam/invoicing-ui/dist/**/*.{js,mjs,cjs}",
  ],
} satisfies Config;

3. Use components

import { Button, Card, CardContent, tokens } from "@yourteam/invoicing-ui";

export function Example() {
  return (
    <Card>
      <CardContent>
        <Button>Click me</Button>
      </CardContent>
    </Card>
  );
}

Dark mode

Toggle the .dark class on <html> (or any ancestor) — all tokens swap to their dark equivalents automatically.

What ships

| Entry | What it is | | ------------------------------------------- | ----------------------------------- | | @yourteam/invoicing-ui | All components, hooks, tokens, cn | | @yourteam/invoicing-ui/tailwind-preset | Tailwind preset (theme + plugins) | | @yourteam/invoicing-ui/styles.css | Tailwind entry + token CSS vars | | @yourteam/invoicing-ui/tokens.css | Just the token CSS vars |

Development

npm install
npm run build       # bundle ESM + CJS + d.ts to dist/
npm run dev         # watch mode
npm run typecheck

The build uses tsup. Output goes to dist/ with react, react-dom, tailwindcss, and tailwindcss-animate left external.

Releasing

This package follows Semantic Versioning and Keep a Changelog.

  1. Make your changes on a branch.

  2. Add an entry under ## [Unreleased] in CHANGELOG.md.

  3. Bump the version:

    • npm version patch — bug fixes only
    • npm version minor — additive, backward-compatible changes
    • npm version major — breaking changes (renamed exports, removed components, changed token names, etc.)
  4. Move the Unreleased block under a new ## [x.y.z] - YYYY-MM-DD heading.

  5. Publish:

    npm publish

    prepublishOnly runs clean + build automatically.

  6. Push the tag created by npm version so the release is traceable:

    git push --follow-tags

What counts as breaking

  • Removing or renaming an exported component, hook, or token.
  • Changing a component's required props or default behavior.
  • Renaming a CSS variable or Tailwind token (--ds-*, color names, etc.).
  • Changing the Tailwind preset in a way that alters existing class output.

Anything else (new components, new props with defaults, new tokens, internal refactors) is minor or patch.