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

@rell333/rellui

v0.1.39

Published

A React component library built on React Aria Components and Tailwind CSS v4

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

rell333rell333

Keywords

reactreact-ariacomponentsui-librarytailwind

Readme

rellui

A personal React component library built on React Aria Components and tailwind-variants, styled with Tailwind CSS v4. Same spirit as RellUI (the GLua/PAC3 component library), for the web.

Every component wraps a real React Aria primitive underneath — accessibility (keyboard nav, ARIA roles, focus management) comes for free from React Aria; rellui adds the visual layer and a compound, dot-notation API (Modal.Trigger, Card.Title, Table.Row) on top.

Install

Inside a project:

npm i @rell333/rellui@lastest

Requires React 19+ and Tailwind CSS v4.

In your globals.css:

@import url('https://fonts.googleapis.com/css2?family=Liter&display=swap');
@import "tailwindcss";
@import "@rell333/rellui/theme.css";
@source "../node_modules/@rell333/rellui/dist";

The @source line is what lets Tailwind generate utility classes from rellui's compiled output — without it, every component renders completely unstyled.

Theming

theme.css defines two layers of design tokens:

Literal palette — decorative colors named for what they are: gold, sage, indigo, blush, clay, charcoal, cream, mint, sand. Use these for anything where "whatever this theme's version of that color is" is the right behavior — backgrounds, borders, icon tiles.

Semantic roles — success, warning, danger, accent. Use these anywhere a meaning has to survive a theme swap. This distinction exists because of a real bug: Chip's first version used literal tokens (sage for success, gold for warning) directly, and it worked fine under the warm theme — but under mono, sage and gold both just become shades of grey, silently breaking every status color at once. The fix was adding a second token layer that each theme defines independently, so success can stay green under mono even though the theme's literal sage doesn't.

Rule of thumb going forward: if a component's color choice is about identity (this is a danger button, this is a success chip), use the semantic token. If it's about decoration (an icon tile, a background tint), the literal palette is fine.

Two themes ship today — warm (the default palette) and mono (black/grey/red) — toggled via a data-theme attribute:

<html data-theme="warm">
document.documentElement.setAttribute("data-theme", "mono")

Adding a third theme means adding a new [data-theme="..."] block defining all thirteen tokens (9 literal + 4 semantic) — nothing in any component needs to change.

Components

Form: Button, TextField, Checkbox, Switch, RadioGroup/Radio, Select, DateField, DatePicker, Calendar, FileUpload, DropZone, FileTrigger

Overlay: Modal, Popover, Menu, Tooltip, Toast/Toaster

Navigation: Breadcrumbs, Tabs, Disclosure/DisclosureGroup

Data display: Card, Table, Chip, Meter, Skeleton, Autocomplete

Every component's props extend the underlying React Aria props (Omit<AriaXProps, "className"> plus a plain className?: string), so anything React Aria supports — isDisabled, validation, controlled/uncontrolled state — works without rellui needing to re-declare it.

Stack

  • React Aria Components — behavior and accessibility
  • tailwind-variants — variant-based styling
  • Tailwind CSS v4 — utility classes, CSS-first theming
  • tsup — build (ESM output, bundled types)
  • Liter (Google Fonts) — default typeface, loaded via theme.css