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

@hanzo/composer

v0.2.0

Published

The composer's material — the lit ring around anything you can type into, as @hanzo/gui components.

Readme

@hanzo/composer

The lit ring around anything you can type into, as @hanzo/gui components. The same material on hanzo.ai, hanzo.chat and hanzo.app.

pnpm add @hanzo/composer
import { Composer, Control, Field } from '@hanzo/composer'

<Composer render="form" onSubmit={send} width="100%" maxW={576} mx="auto">
  <XStack items="center" gap="$1.5" p="$1" rounded="$10">{/* your panel */}
    <Field value={draft} onChangeText={setDraft} placeholder="Ask anything" />
    <Control asChild>
      <Voice voice={voice} />
    </Control>
    <Control type="submit" aria-label="Send" fill>
      <ArrowUp size={15} />
    </Control>
  </XStack>
</Composer>

The host wraps the surface's own panel. This package owns the ring, the halo, the round controls and the field's reset; it owns nothing about what typing does. A host writes no CSS against it: every paint is a gui prop reading a @hanzo/design token.

Composer

| prop | | | |---|---|---| | band | 1.5 | The ring's width, px. Also the host's padding: one number, read twice. | | halo | 6 | How far the halo reaches past the box, px. | | control | 34 | The round controls' box, px, before --density. |

Any gui View prop rides along (render, width, maxW, mx, …). The corner is --radius-composer, with the pill as the floor. The ring rests at .5 and lifts to .8 under a pointer; focus keeps the rest value, because the caret already says where focus is. The halo holds still at .22, blurred 16px.

Control

A circle at the size its Composer names, scaled by --density and floored at 24px (WCAG 2.5.8 AA). size names its own box outside a composer. fill is the send: --primary on --primary-foreground. At rest it is --muted on --text-secondary, and it lifts to --primary under a pointer. A control another package draws wears the shape through asChild.

Field

A gui Input with its chrome off: no border, surface, native appearance or outline, on --text-base, taking the row's spare width down to zero so a long prompt never pushes the controls out of the pill. Any Input prop overrides.

What it obeys

Reads --radius-composer, --density, --text-base, --muted, --text-secondary, --primary, --primary-foreground, --foreground and --muted-foreground from @hanzo/design, each with a fallback.

The sweep is the one stylesheet: a conic angle animates only through @property and @keyframes. It is hoisted once through React's <style>, keyed on the data-slots prism, prism-ring and prism-halo, never a class. Four media queries answer there: prefers-reduced-motion holds the sweep still, prefers-reduced-transparency drops the halo and solidifies the ring, prefers-contrast: more turns the ring into a flat white edge, and forced-colors: active removes both layers for a system-coloured outline.