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

@lily-ui/web-components

v0.1.0

Published

Lily UI — accessible (WCAG 2.1 AAA), framework-agnostic Web Components (custom elements). Light-DOM markup styled by @lily-ui/css; usable in any framework or none.

Downloads

45

Readme

@lily-ui/web-components

Accessible (WCAG 2.1 AAA), framework-agnostic Web Components for Lily UI — custom elements you can drop into any framework (or none). The component set mirrors @lily-ui/react one-for-one — same class names, same DOM, same accessibility.

Light-DOM by design

Lily styling lives in the global @lily-ui/css layer (plain class names + data-theme / data-density). To keep that working, Lily elements render in the light DOM rather than a shadow root: each <lily-*> host is display: contents and renders a real semantic element (e.g. a <button>) with the correct lily-* classes. The result is markup identical to the React/Vue output — fully themeable, with native semantics and event bubbling intact.

Install

pnpm add @lily-ui/web-components @lily-ui/css
// App entry (once):
import '@lily-ui/css/styles';
import '@lily-ui/web-components/define'; // registers all <lily-*> elements
<lily-button status="primary" variant="solid">こんにちは</lily-button>

<lily-card>
  <lily-card-header>Header</lily-card-header>
  <lily-card-body><lily-card-title>Title</lily-card-title>Body</lily-card-body>
</lily-card>

Prefer to register a subset yourself? Skip the /define import and call the registry:

import { defineLilyElements } from '@lily-ui/web-components';
defineLilyElements();

Conventions

  • Tags are kebab-case lily-<name> (parts: lily-<name>-<part>, e.g. lily-card-header).
  • Props are attributes (status, size, variant, block, …). Boolean props are presence-based (<lily-button block loading>).
  • Components that take arrays/objects in React accept a JSON attribute of the same name: <lily-tabs items='[{"id":"a","label":"A","content":"…"}]'>.
  • Native events bubble out of the host (click, input, change). Synthesized events are dispatched as CustomEvent (close, change).
  • Overlays portal to document.body and manage focus trap, scroll lock, and dismissal. Toasts have an imperative API: toast({ message: 'Saved' }).

Theming & tokens

Set data-theme="light|dark" (or omit to follow the OS) and data-density="compact" on an ancestor — see the theming docs. Type-safe token references:

import { cssVar } from '@lily-ui/web-components/tokens';
cssVar('color-primary'); // "var(--lily-color-primary)"

Develop

pnpm --filter @lily-ui/web-components build       # ESM + CJS + d.ts
pnpm --filter @lily-ui/web-components typecheck