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

aronia

v0.4.0

Published

Copy an agent-friendly design language into your repo. `npx aronia add <component> --style <style>`.

Downloads

514

Readme

aronia

Copy an agent-friendly design language into your repo — not a black-box dependency.

aronia copies real, editable component source — tokens, styles, and a thin skin in your framework — into your repo, alongside a machine-readable manifest your coding agent can read as a worked example.

Start by bringing the language in — no style chosen yet:

npx aronia init

That writes aronia/START.md (an optional, agent-run conversation to help you choose a direction), aronia/AGENTS.md (how an agent should build with aronia), and aronia/aronia.manifest.json (the full family menu — no components, no style adopted yet). Then tell your agent:

Start at aronia/START.md. If I already know what I'm building and the style I want, skip it and build; otherwise help me choose. Then match aronia/.

Once a style is chosen, pull components — the first add adopts that style, and later ones need no flag:

npx aronia add button --style swiss   # adopts swiss + your framework
npx aronia add card badge             # same language, no --style needed

Each add writes into aronia/<style>/:

aronia/
  swiss/
    tokens.css     # design tokens (written once per style)
    button.css     # the component's styles — the actual "language"
    Button.tsx     # a thin skin in your framework
  aronia.manifest.json

Usage

aronia init                            # bring the language + onboarding in
aronia add <component...> [options]    # add components; the first add adopts a style

| Option | Description | Default | | --- | --- | --- | | --style <id> | neo-brutalism, glassmorphism, or swiss. Required for the first add; remembered after. | adopted | | --framework <fw> | react, svelte, or html. | detected, else react | | --cwd <dir> | Where to write the aronia/ folder. | current dir | | --registry <src> | Registry URL or local directory. | bundled |

Three design languages, 20 components each; dependencies are pulled in automatically (e.g. toast also adds alert).

Full docs and source: https://github.com/Chukwuka-Osakwe/aronia