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

@abbainitiative/ui

v0.1.0

Published

ABBA Design System — accessible, themeable React components for React and Next.js App Router applications.

Readme

@abbainitiative/ui

React components for Next.js and plain React. No Tailwind, no provider, no config.

Live docs → · GitHub


Install

pnpm add @abbainitiative/ui

React 18.2 or 19 is a peer dependency.

Use it

1. Import the stylesheet once, at the root of your app:

// app/layout.tsx (Next.js) or src/main.tsx (Vite)
import "@abbainitiative/ui/styles.css";

Put it above your own stylesheets so your overrides win.

2. Use the components:

import { Button, Card, CardBody, Heading, Stack } from "@abbainitiative/ui";

export default function Page() {
  return (
    <Card variant="elevated">
      <CardBody>
        <Stack gap={4}>
          <Heading level={1}>Welcome back</Heading>
          <Button>Get started</Button>
        </Stack>
      </CardBody>
    </Card>
  );
}

No transpilePackages, no PostCSS plugin, no theme provider.

What's in it

| | | | -------------- | ---------------------------------------------------------------------- | | Layout | Box Stack Inline Container Grid Separator VisuallyHidden | | Typography | Text Heading Label Code Link | | Buttons | Button IconButton ButtonGroup | | Forms | Input Textarea FormField FormMessage | | Display | Card Badge | | Feedback | Alert Spinner | | Overlays | Dialog DropdownMenu Tabs Toast |

Every component also has its own entry point: @abbainitiative/ui/badge.

Quick examples

<Button variant="danger" loading>Deleting</Button>
<Button asChild><Link href="/signup">Sign up</Link></Button>
<IconButton aria-label="Delete" icon={<TrashIcon />} />

<FormField label="Email" error={error} required>
  <Input type="email" />
</FormField>

<Alert tone="danger" title="Payment failed">Update your card details.</Alert>
<Badge tone="success" dot>Active</Badge>

Every component, with live examples →

Dark mode

Set data-theme="dark" or the class dark on <html>. Both selectors ship, so next-themes works unchanged.

Theming

Every colour, size and radius is a CSS variable. Override what you want, after the ABBA stylesheet:

:root {
  --abba-primary: #4338ca;
  --abba-radius-md: 3px;
  --abba-font-sans: var(--my-font), system-ui, sans-serif;
}

No provider and no runtime, so it works inside Server Components too. Token list →

Next.js

"use client" is placed per component, never at the package root — so importing a Stack does not drag the whole library into your client bundle.

Server-renderable: Box Stack Inline Container Grid Separator VisuallyHidden Text Heading Label Code Link ButtonGroup FormMessage Card Badge Spinner

Bring their own client boundary: Button IconButton Input Textarea FormField Alert Dialog DropdownMenu Tabs Toast

You can render either kind from a Server Component — you just cannot pass a function to one. Next.js guide →

Accessibility

Keyboard interaction, focus management and ARIA relationships ship with each component and are tested, including an automated axe pass in CI. Focus trapping and menu navigation come from Radix, used internally — none of its API is exposed.

Requirements

  • React 18.2 or 19
  • "moduleResolution": "bundler", node16 or nodenext in your tsconfig.json
  • Evergreen Chrome, Edge, Firefox, Safari

MIT © ABBA Initiative