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

@nisli/ui

v0.3.0

Published

shadcn-style component registry and CLI for the Nisli web component framework. Components are copied into your project as source you own.

Readme

@nisli/ui

"shadcn for Nisli." Accessible, themeable components for the Nisli web-component framework — distributed as source copied into your project, not as a runtime dependency. You own the code.

npm install @nisli/core
npm install -D @nisli/ui tailwindcss tw-animate-css
npx nisli-ui init          # writes nisli-ui.json, copies lib/utils.ts + styles/theme.css
npx nisli-ui add button    # copies ui/button.ts (and its registry deps) into your tree

In a Tailwind v4 entry stylesheet, import the copied theme immediately after Tailwind:

@import "tailwindcss";
@import "tw-animate-css";
@import "./nisli-ui/styles/theme.css";

Components are authored with @nisli/core (signals + html templates) and compile to standard custom elements, so they work two ways:

// Nisli composition — typed factory
import { Button } from './nisli-ui/ui/button.js';

html`${Button({ variant: 'outline', children: 'Save' })}`;
<!-- plain HTML — any framework or none -->
<ui-button variant="outline">Save</ui-button>

Requirements

  • @nisli/core >= 0.53
  • Tailwind CSS v4 + tw-animate-css — import the copied styles/theme.css after both build-tool imports. Theming and dark mode work exactly like shadcn/ui: override the CSS variables; add a .dark class.

The networked smoke test for the currently published package runs as a separate CI job and can be invoked locally with pnpm --filter @nisli/ui e2e:npm. Set NISLI_UI_VERSION to verify a specific release.

Design

Architecture and conventions are recorded in ADR 0022; vision, invariants, and roadmap in NORTH-STAR.md. Highlights:

  • Light DOM, no shadow roots. Hosts are layout-transparent (display: contents); styling lives on the inner elements, so Tailwind and design tokens just work.
  • Zero runtime npm dependencies in copied source — vendored cn()/cv() replace clsx/cva.
  • Standards-consumable: attributes as prop fallbacks, light-DOM children projection, native events, data-slot/data-state styling hooks.

Attribution

Component markup, class lists, and behavior are ported from shadcn/ui (MIT) and the Radix Primitives patterns they wrap (MIT).