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

@ibis-design/react

v3.0.0

Published

React component library for the IBIS design system.

Readme

@ibis-design/react

React 18/19 components of the IBIS design system 3.x, built on Skeleton v5 (zag) with the IBIS themes. Same props as @ibis-design/svelte. Client components ("use client"), safe to import from React Server Components.

npm install @ibis-design/css @ibis-design/react
npm install -D tailwindcss @tailwindcss/vite @tailwindcss/forms   # or @tailwindcss/postcss

In the app stylesheet (Tailwind CSS v4):

@import "tailwindcss";
@plugin "@tailwindcss/forms";
@import "@ibis-design/css";
import { Button, Dialog, toast, Toaster } from "@ibis-design/react";
import { useState } from "react";

export function DeleteCase() {
  const [open, setOpen] = useState(false);
  return (
    <>
      <Button onClick={() => setOpen(true)}>Delete</Button>
      <Dialog
        open={open}
        onOpenChange={setOpen}
        role="alertdialog"
        title="Delete this case?"
        footer={
          <>
            <Button variant="secondary" onClick={() => setOpen(false)}>Keep</Button>
            <Button intent="destructive" onClick={() => { setOpen(false); toast.success("Case deleted"); }}>Delete</Button>
          </>
        }>
        <p>This cannot be undone.</p>
      </Dialog>
    </>
  );
}

// once, in the root component:
<Toaster />;

State follows React conventions: controlled value / checked / selected / open / page / sort with on*Change, or default* props for uncontrolled use. Text inputs are native (value + onChange). Content slots are ReactNode props (footer, actions, icon, …).

Components

| Area | Components | |---|---| | Actions | Button, IconButton, CopyButton, TextLink, Menu | | Forms | Field, TextField, TextArea, Select, Combobox, Checkbox, RadioGroup, Switch, FileUpload, Chip, SegmentedControl | | Content | Card, CardHeader, Alert, Badge, Avatar, UserBadge, Logo, Divider, Tooltip, Tabs, DescriptionList, StatCard | | Feedback and overlays | Toaster + toast, Progress, Spinner, Skeleton, SkeletonText, EmptyState, Dialog, Drawer | | Data | Table, DataTable, Pagination, FilterBar | | Layout | AppShell, AuthLayout, PageHeader, Stack, Grid, FormLayout, FormLayoutRow, ThemeToggle, LocaleProvider |

One line per component: llms.txt; every prop: component-manifest.json; page compositions: patterns.md (examples in Svelte; the props are the same). All three ship in this package.

Bring your own icons (lucide-react recommended). Don't import @skeletonlabs/* directly; @ibis-design/eslint-config enforces it.

AI coding agents

llms.txt, patterns.md and component-manifest.json are written for coding agents. Point the agent at them from the app's CLAUDE.md (Claude Code) or AGENTS.md (other agents; Claude Code reads it when CLAUDE.md contains the line @AGENTS.md):

## UI: IBIS design system (@ibis-design/react)

- Build all UI with `@ibis-design/react` components and `@ibis-design/css` tokens. Don't write custom components or
  styles for what the design system covers.
- Before writing or changing UI, read `node_modules/@ibis-design/react/llms.txt` (rules, patterns, components) and
  the matching pattern in `node_modules/@ibis-design/react/patterns.md` (Svelte examples; same props in React).
- Look up exact props in `node_modules/@ibis-design/react/component-manifest.json` instead of guessing them.
- Never import `@skeletonlabs/*` or `@zag-js/*`. Run the linter after UI changes.

To load the rules into every Claude Code session instead of on demand, add the line @node_modules/@ibis-design/react/llms.txt to CLAUDE.md (about 4,000 tokens of context).

Docs

Getting started (theme without flash incl. Next.js, fonts, toasts) · Migrating from 2.x · from 1.x · Storybook (npm run storybook:react)