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

chromium-ui-react

v0.4.3

Published

Chromium-native React component library. Build browser extensions, Electron apps, and Google-adjacent web UIs that look and feel like first-party Chromium surfaces.

Readme

chromium-ui-react

npm types license docs

React components that look and feel like Chromium's native UI.

Built first and foremost for Chromium extension developers who want their popups, side panels, and options pages to feel like first-party Google surfaces rather than generic React apps. Works anywhere React works — including Electron, Tauri, Next.js, Remix, Astro, and Docusaurus.

Chromium UI React showcase — toolbar, sidebar, card with tabs and form, progress, activity list, buttons, chips, badges, and toasts.

Features

  • 21 accessible React components (Button, Input, Toggle, Dialog, Tabs, Menu, Toast, Card, ...)
  • Chromium-authentic design tokens mirroring cr_shared_vars.css
  • Automatic dark mode via prefers-color-scheme, or force it with data-cr-theme="dark"
  • Zero-runtime styling — plain CSS, no CSS-in-JS bundle
  • SSR-safe, tree-shakeable ESM + CJS + .d.ts
  • React 18 and React 19 supported

Install

npm install chromium-ui-react
# or
pnpm add chromium-ui-react
# or
yarn add chromium-ui-react

Peer dependencies: react >= 18 and react-dom >= 18.

Usage

Import the stylesheet once in your app's entry file, then use components anywhere:

// main.tsx / _app.tsx / root layout
import 'chromium-ui-react/styles.css';
import { Button, Input, Card, CardBody } from 'chromium-ui-react';

export default function SignIn() {
  return (
    <Card variant="outlined">
      <CardBody>
        <Input label="Email" placeholder="[email protected]" />
        <Input label="Password" type="password" />
        <Button variant="action">Sign in</Button>
      </CardBody>
    </Card>
  );
}

That's it. Dark mode is already working via prefers-color-scheme.

Tokens without components

If you want the design tokens but plan to write your own components, import the tokens file on its own:

import 'chromium-ui-react/tokens.css';

Then reference the --cr-* custom properties in your own CSS:

.my-custom-panel {
  background: var(--cr-fallback-color-surface);
  color: var(--cr-primary-text-color);
  border-radius: var(--cr-radius-md);
  padding: var(--cr-space-4);
  box-shadow: var(--cr-elevation-1);
}

Browser extension usage

In manifest.json (Manifest V3):

{
  "manifest_version": 3,
  "name": "My Extension",
  "version": "0.1.0",
  "action": { "default_popup": "popup.html" },
  "side_panel": { "default_path": "sidepanel.html" }
}

Bundle with Vite + @crxjs/vite-plugin (recommended) or Webpack. Import chromium-ui-react/styles.css once in your popup/sidepanel entry.

Component overview

| Category | Components | |---|---| | Actions | Button, IconButton, Link | | Forms | Input, Textarea, SearchInput, Select, Checkbox, Radio, RadioGroup, Toggle, ToggleRow | | Tags | Badge | | Surfaces | Card, CardHeader, CardBody, CardFooter, CardTitle, CardDescription | | Layout | Divider, Header, List, ListItem, Table, TableHead, TableBody, TableRow, TableCell, TableHeaderCell | | Navigation | Tabs, TabList, Tab, TabPanel, TabsSimple, Menu, MenuItem, MenuDivider, MenuLabel, PanelStack, PanelView, PanelHeader, PanelRow | | Feedback | Spinner, Progress, Toast, Dialog, Tooltip | | Empty | EmptyState |

Plus the utility cn(...) className helper.

Documentation

Full docs with live previews, prop tables, and a Copy-Markdown-for-your-LLM button on every page:

ztnkv.github.io/chromium-ui-react

The docs also expose the One-page LLM doc designed to be pasted into a coding agent — everything the agent needs to generate Chromium-styled UI from a single prompt.

Source on GitHub: github.com/ztnkv/chromium-ui-react.

Browser support

Chromium-based browsers (Chrome 100+, Edge, Brave, Arc, Opera). Firefox and Safari render fine — the library uses only standard CSS custom properties and modern DOM APIs — but visual parity on non-Chromium browsers is not a design goal.

License

MIT