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

@aizvi/ui

v0.1.1

Published

An open-source React design system for building modern, consistent, and accessible user interfaces.

Downloads

33

Readme

Aizvi/UI

An open-source React design system for building modern, consistent, and accessible user interfaces.

Built with TypeScript, Radix Primitives, and CSS Modules. Radix stays an internal implementation detail, you never import it directly.

Consumer application
        ↓
Public components (@aizvi/ui)
        ↓
TypeScript API + CSS Modules
        ↓
Radix Primitive or native HTML

Install

npm install @aizvi/ui

react and react-dom are peer dependencies (^18.2.0 || ^19.0.0).

Usage

import { Button, Dialog, Input } from "@aizvi/ui";
import "@aizvi/ui/styles.css";

export function Example() {
  return <Button variant="primary">Continue</Button>;
}

@aizvi/ui/styles.css bundles the color palette, semantic tokens, and a base reset alongside every component's styles, import it once, at the root of your app.

Each component is also available as its own subpath, if you'd rather not import from the package root:

import { Button } from "@aizvi/ui/Button";

Themes

Set data-theme on <html> (or any ancestor element) to switch between light and dark:

<html data-theme="light"></html>
<html data-theme="dark"></html>

Falling back to :root styling means light is the default even with no attribute set.

Typography

Roboto is the default font, loaded from nowhere in particular, the package never fetches a font from an external URL. Bring your own Roboto (self-hosted, next/font, a <link> tag, whatever fits your app), or override the token to use something else entirely:

:root {
  --ds-font-family: "Inter", system-ui, sans-serif;
}

Design tokens

Components read from semantic CSS custom properties, never hard-coded colors, spacing, or radii. Override any of them in your own stylesheet to reskin the library:

:root {
  --ds-color-primary: var(--blue-9);
  --ds-radius-md: 0.375rem;
  --ds-space-4: 1rem;
}

See src/styles/tokens.css for the full set (color, spacing, radius, typography, shadows, motion, focus ring).

Components

| Component | Built on | | ---------------------------------------- | ---------------- | | Button, Input, FormField, Textarea, Link | Native HTML | | Heading, Text, Card, Container, Stack | Native HTML | | Dialog, Select, Checkbox, Switch | Radix Primitives | | Tabs, Tooltip, Popover, DropdownMenu | Radix Primitives | | Accordion, Slider | Radix Primitives |

Accessibility

Every component ships with keyboard support, visible :focus-visible styling, correct labeling, ARIA attributes where required, sufficient color contrast, and disabled/loading states. Storybook's accessibility addon runs automated checks against every story.

Development

npm install
npm run dev              # Storybook at localhost:6006
npm run build             # library build (dist/)
npm run build:storybook   # static Storybook site
npm run typecheck
npm run lint
npm run test
npm run generate:palette  # regenerate palette.css from @radix-ui/colors

Package requirements

  • ESM output only, with generated TypeScript declarations.
  • react / react-dom are peer dependencies; Radix primitives are regular dependencies.
  • CSS files are marked as side effects; everything else is side-effect free.
  • Interactive component entry points keep their "use client" directive intact, so Next.js's app router can draw the client boundary correctly.

License

MIT