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

pari-components

v0.3.3

Published

Accessible web component library

Readme

Pari

Storybook npm version install size zero dependencies OpenSSF Scorecard CI license

Accessible web component library. Vanilla TypeScript, no runtime dependencies, unstyled.

Accessibility first

Every component is built to the W3C ARIA Authoring Practices Guide. Keyboard interactions, focus management, and ARIA attributes are handled automatically. You write the markup; Pari handles the behavior.

Components

| Component | What it does | | --------------------- | ------------------------------------------------------------------------------------------------------- | | pari-disclosure | Toggles visibility of a content region. Click the trigger, the panel shows or hides. | | pari-accordion | Groups multiple disclosures. Arrow keys move between headers; Home/End jump to first/last. | | pari-tabs | Manages a tablist and its panels. Handles roving tabindex so only the active tab is in the focus order. | | pari-dialog | Wraps the native <dialog> element. Adds scroll lock on the body and returns focus when closed. | | pari-popover | Thin wrapper around the Popover API. Pairs a trigger button with its popup content. | | pari-nav-disclosure | Dropdown navigation that opens on hover, Enter, Space, or arrow down. Closes when focus leaves. | | pari-notification | Displays a message via the Popover API and announces it to screen readers without moving focus. | | pari-tooltip | Floating label that appears on hover or focus. Never receives focus. Dismisses on Escape or blur. |

Example

<pari-disclosure>
	<button data-trigger aria-expanded="false">What is Pari?</button>
	<div data-content hidden>
		<p>An accessible web component library.</p>
	</div>
</pari-disclosure>

The component keeps aria-expanded, aria-controls, and hidden in sync with the actual state. Once you import the module, the custom element handles everything else.

Browser support

These components use modern platform features. Here's when support landed:

| Feature | Chrome | Firefox | Safari | | ----------------------------------------------------------------- | --------------- | --------------- | ---------------- | | Custom elements (all components) | 67+ (May 2018) | 63+ (Oct 2017) | 12.1+ (Mar 2019) | | <dialog> (pari-dialog) | 37+ (Aug 2014) | 98+ (Feb 2022) | 15.4+ (Mar 2022) | | Popover API (pari-popover, pari-notification, pari-tooltip) | 114+ (May 2023) | 125+ (Apr 2024) | 17+ (Sep 2023) |

Polyfills aren't included. Most components work anywhere Custom Elements v1 is supported. pari-dialog and pari-popover need the native APIs—check your analytics before using them.

Install

npm install pari-components

Usage

ESM (bundler or modern browser)

// Everything
import 'pari-components';

// Or just what you need
import 'pari-components/disclosure';
import 'pari-components/tabs';
import 'pari-components/notification';

Script tag

<script src="/path/to/components.iife.js"></script>

<pari-disclosure>
	<button data-trigger>Show more</button>
	<div data-content hidden>Your content here.</div>
</pari-disclosure>

The IIFE bundle registers all components on load.

Styling

Pari ships no CSS. Style the components however you already style your site—plain CSS, Tailwind, CSS modules, whatever. The components don't inject styles or use shadow DOM, so your selectors work directly on the markup.

Development

npm install
npm run storybook    # Component explorer + docs
npm run build        # Library build (ESM + IIFE)
npm test             # Vitest + Storybook tests

License

MIT