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

flintwork

v0.1.0

Published

A hand-crafted design system with headless primitives, token-driven theming, and built-in accessibility.

Readme

flintwork

A design system built from scratch. Headless primitives with token-driven theming and keyboard-first accessibility.

What this is

Flintwork is a React component library with two layers:

  • Primitives — headless components that handle behavior, keyboard interactions, focus management, and ARIA attributes. No styling opinions. You bring your own CSS.
  • Styled components — a styled layer that consumes the primitives and applies a token-driven visual design. Every style value comes from a design token. Theme switching is a single attribute swap.

The token pipeline is custom-built. JSON token files feed into a build script that outputs CSS custom properties with full theme support. No Style Dictionary, no CSS-in-JS runtime.

Install

pnpm add flintwork

Usage

import { Button } from 'flintwork';
import 'flintwork/tokens';
import 'flintwork/styles';

Token architecture

Tokens follow a three-tier model:

Global    →  raw palette values (blue-500, spacing-4, radius-md)
Semantic  →  intent-based mappings (color-text-primary, color-bg-error)
Component →  component-specific bindings (button-bg, button-text)

Theme switching remaps the semantic layer. Components reference semantic tokens, so swapping [data-theme="dark"] on the root element updates everything without touching component styles.

<div data-theme="dark">
  <!-- all components automatically use dark token values -->
</div>

Token customization

Import the CSS and override any custom property:

:root {
  --fw-color-interactive-default: #6366f1;
}

Development

pnpm install
pnpm build:tokens   # build CSS custom properties from JSON tokens
pnpm build          # build tokens + library
pnpm test           # run tests
pnpm typecheck      # type check without emitting

Project structure

src/
├── tokens/
│   ├── global/         # Tier 1 — raw palette, spacing, typography, radii, shadows
│   ├── semantic/       # Tier 2 — intent mappings, light.json and dark.json
│   └── component/      # Tier 3 — component-specific token bindings
├── primitives/         # Headless components (Phase 2)
├── styled/             # Styled layer consuming primitives (Phase 3)
├── hooks/              # Internal behavior hooks (useFocusTrap, useRovingTabIndex, etc.)
├── utils/              # DOM utilities (portal, merge-refs, etc.)
├── scripts/
│   └── build-tokens.ts # Token build pipeline
└── index.ts            # Public API

Principles

  • Every style value comes from a token. No hardcoded colors, no magic numbers.
  • Accessibility is structural, not bolted on. Primitives enforce correct ARIA and keyboard behavior.
  • Headless first. Behavior and presentation are separate concerns.
  • Zero runtime dependencies. React is the only peer dep.
  • Tree-shakeable. Import what you use, nothing else ships.

License

MIT