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

@homeflare/ui

v0.3.0

Published

HomeFlare brand tokens and shared compositions for apps built on Cloudflare Kumo.

Readme

@homeflare/ui

HomeFlare brand tokens and shared compositions for apps built on Cloudflare Kumo.

bun add @homeflare/ui @cloudflare/kumo react react-dom @phosphor-icons/react

Browser and React surfaces only. Workers, scripts and servers need nothing here — they want @homeflare/kit.

Kumo is a peer, not a re-export

Import Kumo's components directly and granularly:

import { Button } from '@cloudflare/kumo/components/button';
import { Dialog } from '@cloudflare/kumo/components/dialog';

★ This package does not re-export them. A barrel would pull all 44 components into the module graph, so an app using a Button would ship the chart library — which is exactly why Kumo documents the per-component subpaths.

⚠️ Because you import Kumo directly, you declare it. It is a peer here so that one copy wins; a dependency would let two versions coexist, meaning two stylesheets and two Base UI instances in one tree.

Peers: @cloudflare/kumo ^2.13.2 · react 18 or 19 · react-dom. Kumo's own peers: @phosphor-icons/react, plus zod and echarts — both optional, needed only by the components that use them.

Styles

import '@homeflare/ui/styles'; // once, at your app root

Kumo's stylesheet plus HomeFlare tokens (--hf-radius-card, --hf-shell-max-width, --hf-gutter). It replaces import '@cloudflare/kumo/styles' — importing both is harmless but redundant.

Opt-in, never automatic. The JS entrypoint imports no CSS, because a library that does so on your behalf breaks any consumer whose bundler cannot handle CSS imports.

Next.js (App Router)

// app/layout.tsx
import '@homeflare/ui/styles';

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en">
      <body>{children}</body>
    </html>
  );
}

⚠️ Import it in the root layout, not in a client component: a CSS import inside a 'use client' module loads per route rather than once.

Vite / TanStack Start

// src/main.tsx — or the root route module in TanStack Start
import '@homeflare/ui/styles';
import { createRoot } from 'react-dom/client';

No plugin or Tailwind preset is required; Kumo ships plain CSS.

What lands here

Compositions of Kumo parts that more than one app needs — never reimplementations. If Kumo has it, use Kumo's.

⛔ shadcn and Radix stay out: Kumo already occupies that layer, on Base UI. Taking both means two primitive libraries, two styling conventions and two accessibility models.

License

MIT © Timothy Schneider