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

@windforge/ui

v0.1.1

Published

React components for **Windforge** — a composable, configurable, strict design system built on **Radix + Tailwind** with CSS-variable tokens and zero CSS-in-JS runtime.

Readme

@windforge/ui

React components for Windforge — a composable, configurable, strict design system built on Radix + Tailwind with CSS-variable tokens and zero CSS-in-JS runtime.

You build with two surfaces:

  • Components take intent-named props (variant="primary", padding="card", gap="md", tone="muted") that expose only on-system options — className and style are rejected at the type level, so there's no path off-system. The escape hatch is the three layout primitives Box / Stack / Grid, which do accept className (including Tailwind arbitrary values like w-[37%]) and style. So the rare break-glass case stays contained to three named places.
  • Tokens (--wf-* CSS variables, from @windforge/tokens) reskin the whole library at once. A token change can't break a layout.

Install

npm install @windforge/ui

@windforge/tokens comes along as a dependency. react / react-dom (^18.3) are peer dependencies you'll already have in a React app.

Setup

1. Wire the Tailwind preset. It ships the full theme, keyframes, animations, and the tailwindcss-animate plugin, so there's no config to hand-copy:

// tailwind.config.cjs
module.exports = {
  presets: [require('@windforge/ui/tailwind')],
  content: [
    './src/**/*.{ts,tsx}',
    './node_modules/@windforge/ui/src/**/*.{ts,tsx}', // scan the library's classes
  ],
}

2. Load the token CSS and wrap your app in ThemeProvider:

import { ThemeProvider, Toaster } from '@windforge/ui'
import '@windforge/tokens/tokens.css'

export function Root() {
  return (
    <ThemeProvider defaultMode="system" persist>
      <App />
      <Toaster />
    </ThemeProvider>
  )
}

Use it

import { Stack, Card, Text, Button } from '@windforge/ui'

export function Example() {
  return (
    <Card padding="card">
      <Stack gap="md">
        <Text>Composed entirely from on-system props — no className.</Text>
        <Button variant="primary">Continue</Button>
      </Stack>
    </Card>
  )
}

Re-skin the brand at runtime

A brand is one 50→950 color ramp; themeVars derives every role-named --wf-color-brand-* variable from it (WCAG-aligned and mode-aware) and can swap the font and radius in the same call. Because it's applied at the document root, the swap reaches portaled overlays too:

import { ThemeProvider, themeVars, type Ramp } from '@windforge/ui'

const brand: Ramp = {
  50:  '#eff6ff', 100: '#dbeafe', 200: '#bfdbfe', 300: '#93c5fd', 400: '#60a5fa',
  500: '#3b82f6', 600: '#2563eb', 700: '#1d4ed8', 800: '#1e40af', 900: '#1e3a8a',
  950: '#172554',
}

<ThemeProvider tokens={(mode) => themeVars({ brand, fontSans: 'Inter, sans-serif' }, mode)}>
  <App />
</ThemeProvider>

@windforge/ui re-exports the entire @windforge/tokens surface, so themeVars, brandVars, brandRamp (the default indigo ramp), and the wf* token constants all import from here directly.

What's included

Primitives (Button, Card, Input, Badge, Text/H1H6…), Radix-backed interactive components (Select, Dialog, Tooltip, Tabs, Popover, DropdownMenu, Command, DatePicker…), data display (Table, DataTable, Chart), layout primitives (Box, Stack, Grid) and shells (AppShell, SideNav, AppBar). Use lucide-react for icons.

License

MIT