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

@fezchat/ui

v0.1.1

Published

The fez app's own shell/form/identity primitives as React components — an extension built from them renders the identical DOM and follows every theme for free.

Readme

@fezchat/ui

The fez app's own UI primitives, as React components — so a GUI extension looks like a built-in view instead of a stranger's iframe.

Each component renders the exact class names and theme tokens the host app uses, so an extension built from them is visually indistinguishable from the app and follows every theme change for free.

Install

npm install @fezchat/ui
# pairs with the theme-wired utility classes:
npm install -D @fezchat/tailwind-preset

react is a peer dependency — your extension bundles its own React under the fez mount model.

Components

| Component | Use it for | |---|---| | <Page wide?> | The top-level page shell (fills rail → side pane). | | <PageHeader title subtitle? fact? action?> | A page header with the app's rule and one live fact. | | <EmptyState line how?> | A full-voice empty state, not a grey italic line. | | <Field label hint?> | A labelled form control with a hint. | | <Row active? onClick?> | A selectable row; active draws the ember-notch idiom. | | <Chip tone?> | A skill/label chip. | | <Avatar pk name? size?> | The pubkey-generated identity sprite. |

Usage

Under the fez mount model, your extension mounts its own React root into a host-provided node:

import { createRoot } from "react-dom/client";
import { Page, PageHeader, EmptyState } from "@fezchat/ui";

function App() {
  return (
    <Page wide>
      <PageHeader title="My tool" subtitle="Built from @fezchat/ui." fact="ready" />
      <div className="bg-fez-surface text-fez-fg rounded-md p-4">
        <EmptyState line="Nothing here yet." how="Wire up your view." />
      </div>
    </Page>
  );
}

export function activate(api) {
  api.registerNavView("my-tool", { glyph: "◆", label: "My tool" }, (host) => {
    const root = createRoot(host);
    root.render(<App />);
    return () => root.unmount();
  });
}

Custom bits use the fez-* Tailwind utilities from @fezchat/tailwind-preset, which resolve to the live theme tokens — never a bare hex.

Scaffold one in a command

fez create my-tool --gui

emits a working extension already built from @fezchat/ui.

Boundary

This library extracts the reusable shell / form / identity primitives and the app's idioms (the ember notch, identity-gets-a-face, the empty-room voice). Per-view styling stays in your extension — via fez-* utilities or a CSS module. The shell primitives are shaped for a top-level page; for content embedded inside a nav view with a custom layout, hand-authored markup on the app's classes may fit better.