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

@ui-organized/react

v5.1.0

Published

React component library for the ui-organized design system, built on Ark UI.

Readme

@ui-organized/react

React component library for the ui-organized design system, built on Ark UI and themed entirely through design tokens (CSS custom properties from @ui-organized/tokens).

Install

npm install @ui-organized/react @ui-organized/tokens

react and react-dom (>=18) are peer dependencies.

Icons

Icon libraries are optional peers, and genuinely so: this package imports none of them. Install the one you want and register it with a single import.

npm install lucide-react        # or @tabler/icons-react, or @heroicons/react
// once, near your app entry
import "@ui-organized/react/icons/lucide";
import { Icon, IconProvider } from "@ui-organized/react";

<IconProvider library="lucide" style="outline">
  <Icon name="search" label="Search" />
</IconProvider>

The subpath is the only module that touches lucide-react, so the two libraries you didn't choose are never resolved — not at install, not at build. Forget the import and <Icon> renders nothing and logs the line to add.

Prefer not to rely on import side effects? Pass the set explicitly:

import { lucideIcons } from "@ui-organized/react/icons/lucide";

<IconProvider library="lucide" icons={lucideIcons}>

You can also hand <Icon> a component directly, which needs no registration and no canonical name:

import { Rocket } from "lucide-react";

<Icon name={Rocket} label="Launch" />

Usage

Import the stylesheets once, at your app entry, in this order:

// src/main.tsx
import "@ui-organized/tokens/variables.css";  // 1. token baseline
import "@ui-organized/react/styles";          // 2. component styles
import "./styles/theme.css";                  // 3. your theme — last, so it wins

Order is load-bearing. A theme and the baseline both declare on :root, and :root vs :root is a specificity tie — decided by source order. Import the theme earlier and the baseline silently wins.

@ui-organized/react/styles.css is exported as an alias of /styles, so either spelling resolves. Both carry TypeScript types, so neither needs a declare module shim in your project.

import { Button } from "@ui-organized/react";

export function Example() {
  return <Button intent="primary">Save</Button>;
}

Theming

Components reference semantic roles--color-surface-primary, --color-interactive-primary-default — never literal colours, so re-theming means redefining those properties.

token-contract.json ships with this package: the complete, generated list of every custom property the components consume but don't define. It's derived from the component CSS itself, so it can't fall out of date with the library.

Light and dark ship together and are switched by attribute, not by re-import:

document.documentElement.setAttribute("data-theme", "dark");

Pin the default in your HTML (<html data-theme="light">) so the first frame paints correctly, before any JavaScript runs.

Full guide, including the three ways to produce a theme: https://uiorganized.com/docs/theming.

License

Apache-2.0