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

@zerotal/flow-ui

v1.8.1

Published

Copy-in UI component registry for Flow (Zerotal's reactive SSR layer).

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mbilisphe13mbilisphe13

Keywords

zerotalbuntypescriptframework

Readme

@zerotal/flow-ui

Themeable components for Flow — re-theme by overriding CSS variables, not by editing components.

Styled wrappers compose Flow's accessible headless primitives; all classes are driven by token-backed variants, so you re-theme by overriding CSS variables. You can also "own the code" and copy components into your app via the flow CLI.

Part of the Zerotal framework. Requires Bun ≥ 1.3.14.

Installation

bun add @zerotal/flow-ui

Install the theme

After Tailwind in your app's CSS:

@import "tailwindcss";
@import "@zerotal/flow-ui/theme.css";

This registers the design tokens (--background, --primary, --border, --radius, …) under :root (light) and .dark, and maps them to Tailwind utilities via @theme inline (bg-background, text-foreground, border-border, ring-ring, rounded-md, …). Toggle dark mode by adding the .dark class to <html>. The default palette is a neutral greyscale.

Use components

import { Button } from "@zerotal/flow-ui";

<Button onClick={this.save}>Save</Button>
<Button variant="destructive" size="sm" onClick={() => (this.open = true)}>Delete</Button>
<Button variant="outline" class="w-full">Full width</Button>

Every component forwards onClick/flow:* directives and arbitrary attrs to the underlying element, so server actions and client expressions work exactly as in plain Flow. A class prop is always merged last (via cn → tailwind-merge), so your overrides win.

Own the code — the flow CLI

Prefer to copy components into your app instead of importing the package? Register the provider once, then scaffold:

// bootstrap/providers.ts
import { FlowUiProvider } from "@zerotal/flow-ui";
const providers = [/* … */ FlowUiProvider];
bun zt flow:list                  # browse the 20 components
bun zt flow:init                  # drop cn/gva utils + wire the theme import
bun zt flow:add button,card,dialog  # copy components into app/flow/components/ui/
bun zt flow:add --all             # copy everything
bun zt flow:add button --force    # overwrite an existing file
bun add clsx tailwind-merge          # the copied cn util needs these (the CLI reminds you)

Copied files land in app/flow/components/ui/ with the shared utils in ui/lib/; their ../utils/* imports are rewritten to the local ./lib/* automatically. You own and edit the result — you own the code outright.

Utilities

  • cn(...inputs) — clsx + tailwind-merge; conflicting Tailwind utilities resolve so the last one wins.
  • gva(base, config) — a tiny class-variance-authority clone: variants, defaultVariants, and compoundVariants. Used to author component variant maps.

Status

Shipped:

  • Foundation: cn, gva, theme tokens (neutral + dark).

  • Leaf components: Button, Badge, Card (+ CardHeader/CardTitle/CardDescription/ CardContent/CardFooter), Input, Textarea, Label, Separator, Skeleton, Avatar.

  • Restyles over headless/native primitives: Switch, Checkbox, Select, RadioGroup.

  • Standalone token-themed builds (over Flow's proven Alpine/flow:* directives + client runtimes flowMenu/flowTabs): Dialog, Sheet, DropdownMenu (+ Item/Label/Separator), Tabs, Alert (+ AlertTitle/AlertDescription), Tooltip, Table. These are built fresh rather than wrapping Flow's Modal/Drawer/Dropdown/etc., which bake literal gray colours and append class by string concat, so they can't be re-themed by wrapping.

  • Re-exports: the remaining flow headless primitives (Listbox, Combobox, Popover, Accordion, Disclosure, Field, Fieldset, …) so this is a single import surface.

  • CLI + registry (Phase 3): flow:list / flow:init / flow:add copy components into an app (the "own the code" model), via FlowUiProvider + the registry.

  • Docs site (Phase 4): bun run docs:gen generates a doc page per component into docs/components/ (install · live preview · usage · props), served by the docs app with the flow-ui theme wired in. Doc specs + pure markdown renderers live in src/docs/.

  • Showcase migration (Phase 5): the example app's ComponentsPage is built entirely from flow-ui, covered by an SSR integration test.

All planned phases (0–5) are complete.

Scripts

bun test        # unit tests
bun run typecheck

Documentation