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

@tundralibs/ui

v0.10.0

Published

HTML + CSS + JS component and layout library; first-class UI layer for rAPId. The npm package carries the compiled dist/ bundle (served by jsDelivr); the TypeScript templates are published to JSR.

Readme

@tundralibs/ui

HTML + CSS + JS component and layout library, and the first-class UI layer for rAPId. Plain <link>/<script> consumers get a themeable, CSP-clean bundle; a rAPId app gets typed, escaped-by-default templates for every component and layout, plus a document shell and error pages that plug straight into Application.initialize.

  • Components (44): buttons, inputs, forms, data table, combobox, command palette, date picker, OTP, modal, toasts, tabs, menus, charts (every ApexCharts type, pinned, on the library's tokens), …
  • Layouts (8): stacked, sidebar, rail, split, article, docs, auth, focus — each defined at every viewport band from phones to ultrawide.
  • Themes: tokens only. A theme is one stylesheet loaded after the bundle; dark mode is built in.

Plain HTML

<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@tundralibs/[email protected]/dist/ui.css">
<script src="https://cdn.jsdelivr.net/npm/@tundralibs/[email protected]/dist/ui.js" defer></script>

dist/ is also in the npm package for self-hosting.

rAPId

import { Application } from "@tundralibs/rapid";
import { createCoreTemplate } from "@tundralibs/ui/templates/core";
import { createLayoutTemplate } from "@tundralibs/ui/templates/layout";
import { errorTemplates } from "@tundralibs/ui/templates/errors";
import { Card } from "@tundralibs/ui/card";

const app = await Application.initialize({
  name: "my-app",
  ui: {
    core: createCoreTemplate(), // assets from the versioned CDN, with SRI
    layout: createLayoutTemplate({ brand: "Acme", navLinks: [{ href: "/", label: "Home" }] }),
    errorTemplates,
    prefer: "html",
  },
});
app.get("/", { template: Home }, () => ({ content: {} }));

createCoreTemplate({ assets: "/ui" }) self-hosts instead — copy the bundle with copyUiAssets() from @tundralibs/ui/assets and mount it with server.static: { "/ui": { root, fingerprint: true } }.

Every server-driven component (combobox, command palette, date picker, sortable tables, pagination, lazy regions, validated forms, toasts) speaks rAPId's data-* swap contract and needs no client glue. The example app under examples/app/ wires all of them; run it with deno task app.

Documentation

Also browsable on the wiki, synced from docs/ on every push.

  • Getting started — install (CDN, self-host, JSR), a first page, how the bundle is built.
  • Recipes — real pages as rAPId routes and as plain HTML: app shell, sign-in, dashboard, invoices with bulk actions, uploads with progress, search, notifications, an international contact form with flags.
  • Components — a tour of every component with usage.
  • Layouts — the eight page frames and how they respond.
  • rAPId integration — the shell, swaps, forms, history, the example app.
  • Theming — tokens, dark mode, cascade layers, custom partials.
  • Charts.
  • Reference — every export, generated from the sources.

Development

deno task build        # dist/ui.css, dist/ui.js, version.ts
deno task build:demos  # static demo pages under demo/ — open demo/index.html
deno task test         # every browser suite (needs Chrome; CHROME_PATH)
deno task app          # the rAPId example app on :8010

demo/index.html links the catalogue (every component in every declared variant, size, tone and state, one page per group — CI fails if a component or variant is missing from it), the eight layouts, and the admin sample.

The same tooling runs on Node (npm run … via tsx) and Bun (bun run bun:…). See CLAUDE.md for the full contract and conventions.

License

MIT