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

@pziel/pureui

v0.19.0

Published

Shared React component library for the pure* apps (purerequest, purequery, ...). Radix-ui composed components + Tailwind v4 design tokens.

Readme

pureui

Shared React component library for the pure* desktop apps (purerequest, purequery, and future ones). One source of truth for components and design tokens so every app looks and behaves consistently.

Built with React 19 + TypeScript, Vite (library mode), Tailwind CSS v4, and Radix-based composed components. Previewed with Storybook.

Prerequisites

  • Node.js - version pinned in .nvmrc. Run nvm use before any npm command.
  • npm (this repo is outside ~/projects/as24/).

Setup

nvm use
npm install

Commands

| Command | Description | | --- | --- | | npm run build | Typecheck + build the library to dist/ (ESM index.js + index.d.ts + styles/theme.css). | | npm run dev | Rebuild the library on change (vite build --watch). | | npm run storybook | Component workshop at http://localhost:6006. | | npm run build-storybook | Static Storybook build (storybook-static/). | | npm run lint | Biome check (lint + format + import sort). | | npm run lint:fix | Biome check with safe autofixes applied. | | npm run typecheck | tsc --noEmit. | | npm run format | Biome format write. | | npm test | Behavior tests (Vitest, run once). | | npm run test:watch | Vitest in watch mode. |

Layout

src/
  index.ts              public barrel (Button, buttonVariants, cn, types)
  components/<name>/     one folder per component: <name>.tsx, <name>.stories.tsx, __tests__/
  lib/utils.ts          cn() class-merge helper
  styles/theme.css      shared design tokens (oklch, no-radius)
  test/setup.ts         Vitest + Testing Library setup
docs/
  design.md             shared visual contract
  composed-components.md the component composition rule (read before building)
  adr.md, learnings.md
.storybook/             Storybook (react-vite) config

Consuming from an app

Publishing to a registry is deferred (see docs/adr.md, ADR-001). Until then, link locally.

  1. Add the dependency (local link while publish is deferred):

    // app package.json
    "dependencies": {
      "@pziel/pureui": "file:../pureui"
    }
  2. Import the design tokens once (e.g. in the app entry CSS/TS):

    import "@pziel/pureui/styles/theme.css";

    The consuming app must run Tailwind CSS v4 - the library ships utility class names + token CSS, not precompiled utilities.

  3. Use components:

    import { Button } from "@pziel/pureui";
    
    <Button variant="outline">Click</Button>;
    <Button asChild><a href="/x">Go</a></Button>;

react and react-dom are peer dependencies - the app provides them; React is never bundled into the library.

Consuming the shared tooling config

pureui also ships the base tooling config the pure* apps share, so each app extends one source instead of copying biome.json/tsconfig*/vite/vitest per repo. The JSON presets use native extends; the Vite/Vitest presets are factory functions (raw .ts config under node_modules can't be type-stripped, so they ship compiled).

// app biome.json
{ "extends": ["@pziel/pureui/biome"] }

// app tsconfig.json
{ "extends": "@pziel/pureui/tsconfig", "compilerOptions": { "paths": { "@/*": ["./src/*"] } } }

// app tsconfig.node.json
{ "extends": "@pziel/pureui/tsconfig-node" }
// app vite.config.ts
import { createTauriViteConfig } from "@pziel/pureui/vite";

export default createTauriViteConfig({
  appUrl: import.meta.url,
  devPort: 1430,
  hmrPort: 1421,
});
// app vitest.config.ts
import { createVitestConfig } from "@pziel/pureui/vitest";

export default createVitestConfig({ appUrl: import.meta.url });
// overridable: setupFiles, include, inlineDeps

vite, vitest, @vitejs/plugin-react, @tailwindcss/vite are optional peer dependencies - only apps that import ./vite/./vitest need them installed. components.json is not shareable (shadcn has no extends); keep it copied per app.

Building components

Read docs/composed-components.md and docs/design.md first. Every component is composed (Radix-style: compound parts + asChild/Slot), variants via cva, className merged via cn, no rounded corners.