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

@sangisalarp/ui

v0.1.2

Published

Playful neo-brutalist React component kit

Readme

@sangisalarp/ui

Playful neo-brutalist React 19 components with a Tailwind CSS v4 theme.

Install and import

@sangisalarp/ui is a library: installing it adds dependencies but never scaffolds an app, creates source files, or adds a visible screen. For a fresh folder, use the create-doodle-app CLI quick start; for manual setup, start with the root quick start.

npm install @sangisalarp/tokens @sangisalarp/icons @sangisalarp/ui

Import tokens before the precompiled component stylesheet:

import "@sangisalarp/tokens/css/tokens.css";
import "@sangisalarp/ui/styles.css";
import { Button } from "@sangisalarp/ui";

export function Example() {
  return <Button variant="sun">use doodles</Button>;
}

styles.css is the zero-configuration path: it bundles Tailwind preflight, the Doodle theme, and the utilities used by the published components. If your app owns Tailwind, import @sangisalarp/ui/theme.css instead and add an @source entry for node_modules/@sangisalarp/ui/dist; do not import both stylesheets. The full setup and a copy-paste example are in the root README.

Exports

The package exports Button, Badge, Tag, Card/CardHeader/CardTitle/CardDescription/CardContent/CardFooter, Avatar, Input, Textarea, Select, Checkbox, Radio, Switch, Alert, Progress, Tabs, TabPanel, Tooltip, and Modal.

Most components extend their native HTML props and accept className for local composition. Notable APIs are:

  • Button: variant (solid, sun, terra, sky, outline, ghost) and size (sm, md, lg). Its default type is button.
  • Card: optional tone, tape, and numeric tilt props.
  • Avatar: src/alt or a fallback, plus shape, size, and tone.
  • Input/Textarea: invalid sets aria-invalid and the error border; provide the associated label and message in your form.
  • Tabs: pass items, then render matching TabPanel value children inside it.
  • Modal: controlled open and onClose, with optional title and footer; it uses Radix Dialog for focus management and Escape/overlay dismissal.

Native controls remain keyboard and screen-reader friendly when consumers provide labels, names, descriptions, and error text. The theme adds visible focus rings and reduces motion when prefers-reduced-motion is enabled.

Development

npm run build -w @sangisalarp/ui
npm run typecheck -w @sangisalarp/ui

The package depends on @sangisalarp/icons at the same release line. Keep tokens, icons, and UI versions aligned when upgrading; the root upgrade guide covers the Changesets workflow.