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

@aurora-ds/lib-test

v0.0.3-dev.1

Published

A React 19 UI kit built with Radix primitives and a Vanilla Extract design system.

Readme

@my-org/ui-kit

A React 19 UI kit built with Vite 8 (library mode), Vanilla Extract (zero-runtime, typed CSS-in-TS) and Radix UI primitives. Components are previewed with Storybook.

Features

  • ⚛️ React 19 + TypeScript, ships ESM + CJS + type declarations
  • 🎨 Vanilla Extract design system — a fully typed token theme (colors, spacing, radius, font sizes/weights, shadows, z-index)
  • 🧩 Radix-based components styled with Vanilla Extract recipe() (the typed replacement for cva), composed with clsx
  • 📚 Storybook for interactive component docs
  • ✅ ESLint flat config (typescript-eslint, react-hooks, jsx-a11y, storybook) + Prettier

Install (in a consuming app)

yarn add @my-org/ui-kit react react-dom

Import the stylesheet once (e.g. in your root layout/entry):

import '@my-org/ui-kit/styles.css';

Then use components:

import { Text } from '@my-org/ui-kit';

export function Example() {
  return (
    <>
      <Text variant="h1">Hello world</Text>
      <Text variant="muted">A typographic primitive.</Text>
      <Text variant="code">@my-org/ui-kit</Text>
    </>
  );
}

Theming

The design system is the single source of truth for tokens, organised by category under src/theme/tokens/ (colors.ts, spacing.ts, radii.ts, typography.ts, shadows.ts, zIndex.ts, motion.ts) and built on top of a primitive OKLCH palette.ts. The typed contract and the light/dark theme registration live in src/theme/contract.css.ts.

The kit ships with complete light and dark themes. Dark mode follows the OS by default (prefers-color-scheme) and can be forced per-subtree:

<html data-theme="dark"> ...   <!-- force dark -->
<html data-theme="light"> ...  <!-- force light -->
<html> ...                     <!-- auto: follow the OS -->

Tokens are available two ways:

1. Typed vars (inside *.css.ts, fully autocompleted):

import { style } from '@vanilla-extract/css';
import { vars } from '@my-org/ui-kit';

export const card = style({
  backgroundColor: vars.color.card,
  color: vars.color.cardForeground,
  padding: vars.space.lg,
  borderRadius: vars.radius.md,
  boxShadow: vars.shadow.sm,
});

2. Plain CSS variables — every token is emitted on :root with a stable, human-readable name derived from its path (--color-primary, --space-md, --radius-sm, …). Use them in any stylesheet, or override them to retheme:

:root {
  --color-primary: oklch(0.55 0.2 250); /* rebrand the whole kit */
  --radius-md: 0.25rem;
}

Both stay in sync automatically — overriding a CSS variable also updates every component that references it through vars.

Components

Text

Polymorphic typography primitive.

| Prop | Type | Default | Description | | ---------- | --------------------------------------------------------------------------------------------- | ------- | -------------------------------------------- | | variant | h1 \| h2 \| h3 \| h4 \| p \| lead \| large \| small \| muted \| blockquote \| code | p | Visual style + default semantic HTML element | | weight | normal \| medium \| semibold \| bold | — | Font weight override | | align | left \| center \| right | — | Text alignment | | truncate | boolean | — | Truncate overflow with ellipsis | | as | React.ElementType | — | Override the rendered element |

Scripts

| Command | Description | | ---------------------- | -------------------------------------------- | | yarn dev | Build the library in watch mode | | yarn build | Type-check and build (ESM, CJS, d.ts, CSS) | | yarn storybook | Run Storybook dev server on port 6006 | | yarn build-storybook | Build the static Storybook site | | yarn lint | Run ESLint | | yarn typecheck | Type-check without emitting | | yarn format | Format with Prettier |

Publishing

yarn build produces dist/. The prepublishOnly hook runs the build automatically, and files limits the published package to dist/.

yarn publish --access public

Adding more components

Place new components under src/components/<group>/<name>/ (e.g. actions/, foundation/), re-export them from src/index.ts, and add a *.stories.tsx file next to each component. Define styles in a colocated *.styles.css.ts file using Vanilla Extract recipe() / style() and the design tokens (vars), then compose class names with the mergeClassNames() helper.