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

@aria-ui/elements

v0.1.8

Published

Unstyled Light-DOM-Only Web Components

Readme

@aria-ui/elements

A set of unstyled, accessible Light-DOM-Only Web Components for building user interfaces. Inspired by Radix UI and Ark UI, but shipped as native custom elements that work in any framework — or in plain HTML.

Playground: https://aria-ui.pages.dev/

Features

  • Light DOM only. No Shadow DOM, so your global stylesheet, Tailwind classes, and selectors like [aria-selected="true"] or [data-active] apply directly to the elements you put on the page.
  • Unstyled by design. Every component ships zero CSS. State is exposed via standard ARIA attributes and data-* attributes for you to style however you like.
  • Built on the WAI-ARIA APG. Keyboard interactions, focus management, and ARIA roles follow the WAI-ARIA Authoring Practices Guide patterns.
  • Composable parts. Each component is split into focused custom elements (*-root, *-trigger, *-popup, *-positioner, *-item, …) that communicate through a shared store.
  • Framework-agnostic. Use the elements directly in HTML, or generate framework wrappers with @aria-ui/cli for React, Vue, Solid, Preact, and Svelte.

Components

| Component | Custom elements | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Listbox | aria-ui-listbox-root, aria-ui-listbox-item, aria-ui-listbox-empty | | Menu | aria-ui-menu-root, aria-ui-menu-trigger, aria-ui-menu-positioner, aria-ui-menu-popup, aria-ui-menu-item, aria-ui-menu-submenu-root, aria-ui-menu-submenu-trigger | | Popover | aria-ui-popover-root, aria-ui-popover-trigger, aria-ui-popover-positioner, aria-ui-popover-popup | | Tooltip | aria-ui-tooltip-root, aria-ui-tooltip-trigger, aria-ui-tooltip-positioner, aria-ui-tooltip-popup |

Installation

npm install @aria-ui/elements
# or
pnpm add @aria-ui/elements

Quick start

Register every component with a single call:

import { registerElements } from '@aria-ui/elements'

registerElements()

Then use the elements anywhere in your HTML:

<aria-ui-popover-root>
  <aria-ui-popover-trigger tabindex="0">Open popover</aria-ui-popover-trigger>
  <aria-ui-popover-positioner>
    <aria-ui-popover-popup>
      <p>Hello from a popover!</p>
    </aria-ui-popover-popup>
  </aria-ui-popover-positioner>
</aria-ui-popover-root>

Listbox example

<aria-ui-listbox-root>
  <aria-ui-listbox-item value="apple">Apple</aria-ui-listbox-item>
  <aria-ui-listbox-item value="banana">Banana</aria-ui-listbox-item>
  <aria-ui-listbox-item value="cherry">Cherry</aria-ui-listbox-item>
</aria-ui-listbox-root>
const listbox = document.querySelector('aria-ui-listbox-root')!
listbox.addEventListener('valueChange', (event) => {
  console.log('Selected:', event.detail)
})

Menu example

<aria-ui-menu-root>
  <aria-ui-menu-trigger tabindex="0">Actions</aria-ui-menu-trigger>
  <aria-ui-menu-positioner>
    <aria-ui-menu-popup>
      <aria-ui-menu-item value="cut">Cut</aria-ui-menu-item>
      <aria-ui-menu-item value="copy">Copy</aria-ui-menu-item>
      <aria-ui-menu-item value="paste">Paste</aria-ui-menu-item>
    </aria-ui-menu-popup>
  </aria-ui-menu-positioner>
</aria-ui-menu-root>

Tree-shakable subpath imports

Each component is also published under its own subpath, so you can register only the parts you need:

import { registerListboxRootElement, registerListboxItemElement } from '@aria-ui/elements/listbox'

registerListboxRootElement()
registerListboxItemElement()

Available entry points:

  • @aria-ui/elements — full bundle plus registerElements()
  • @aria-ui/elements/listbox
  • @aria-ui/elements/menu
  • @aria-ui/elements/popover
  • @aria-ui/elements/tooltip
  • @aria-ui/elements/overlay — shared overlay primitives

Setting props

Every prop is available as both an HTML attribute and a JS property. Complex values (arrays, objects, null) are stored as JSON:

<!-- Via attributes -->
<aria-ui-listbox-root multiple values='["apple","banana"]'>
  <aria-ui-listbox-item value="apple">Apple</aria-ui-listbox-item>
  <aria-ui-listbox-item value="banana">Banana</aria-ui-listbox-item>
</aria-ui-listbox-root>
// Via JS properties
const listbox = document.querySelector('aria-ui-listbox-root')!
listbox.multiple = true
listbox.values = ['apple', 'banana']

Styling

Components expose their state through standard accessibility attributes and a few data-* attributes:

| Attribute | Used by | Meaning | | ------------------------------- | ----------------------------- | ------------------------------------------------------------------------- | | aria-selected="true" | listbox items | The option is selected | | aria-expanded="true" | popover/menu/tooltip triggers | The overlay is open | | aria-disabled="true" | any element | The element is disabled | | data-active | listbox items, menu items | The element is the currently highlighted option (aria-activedescendant) | | data-state="open" \| "closed" | overlay popups | Overlay open state, useful for transitions |

Example with Tailwind:

<aria-ui-listbox-item
  value="apple"
  class="block px-3 py-2 cursor-pointer hover:bg-blue-50 aria-selected:bg-blue-100 data-active:outline-2 data-active:outline-blue-500"
>
  Apple
</aria-ui-listbox-item>

Events

Components dispatch standard DOM events whose payload lives on the detail property:

| Event | Dispatched by | detail | | -------------- | ----------------------- | ------------ | | valueChange | listbox (single select) | string | | valuesChange | listbox (multi-select) | string[] | | openChange | popover, menu, tooltip | boolean | | select | menu item, listbox item | (no payload) |

valueChange / valuesChange are cancelable — call event.preventDefault() to take over the state yourself and run the listbox in a controlled mode.

Using with frameworks

For React, Vue, Solid, Preact, and Svelte you can generate typed wrapper components with @aria-ui/cli, which handles attribute/property mapping and converts DOM events into idiomatic framework callbacks.

License

MIT