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

@loomidev/theme

v0.3.0

Published

Shared design tokens + Tailwind theme source for the loomi component library. Defines the overridable `--loomi-*` custom property slots.

Readme

@loomidev/theme

The shared design tokens for the LoomiUI component library. Every component depends on this package; you rarely import it directly.

It provides:

  • themeStyles — a Lit CSSResult containing the :host block that declares the default value for every palette slot (plus a small Shadow-DOM-scoped reset). Components put it first in static styles so var(--loomi-*) references resolve.
  • The paletteLOOMI_COLORS, LOOMI_SHADES, the LoomiColor / LoomiShade types, and the isLoomiColor() guard.
  • tailwind-colors.css — a Tailwind @theme inline mapping (no hex) for authoring components against the --loomi-* slots in your editor.
import { themeStyles, LOOMI_COLORS, type LoomiColor } from "@loomidev/theme";

class MyComponent extends LitElement {
  static styles = [themeStyles, myCompiledStyles];
}

The built-in palette colors are primary, secondary, info, success, error, warning, and gray. info uses Tailwind's blue ramp by default and can be customized through --loomi-info-50 to --loomi-info-950.

Accessibility

For the library-wide baseline, see Foundations — Accessibility.

Responsive behavior

For the shared container and viewport rules, see Foundations — Responsive behavior.

Dark mode

For theme activation, token overrides, and contrast guidance, see Foundations — Dark mode.

The token model

The single source of truth is palette.json: the list of color names, the tonal shades, and the Tailwind ramp each color borrows its default values from. scripts/build-tokens.mjs reads it and generates:

| Generated | Contents | | ------------------------------ | ---------------------------------------------------------------------------------------- | | src/generated/tokens.css.ts | themeStyles:host { --_loomi-<color>-<shade>-default: … } | | src/generated/palette.gen.ts | The typed LOOMI_COLORS / LOOMI_SHADES consts | | src/tailwind-colors.css | @theme inline { --color-<c>-<s>: var(--loomi-<c>-<s>, var(--_loomi-<c>-<s>-default)) } |

Why two tiers of variable?

Defaults are stored in private --_loomi-*-default slots, not the public --loomi-* slots. If the public slot were declared on :host, that element-local declaration would beat a value inherited from the consumer's :root, breaking global overrides. By declaring only the private default and referencing var(--loomi-X, var(--_loomi-X-default)) in utilities, the public slot stays free to be set from :root and inherit through the shadow boundary.

Override the public slot, never the private one:

:root {
  --loomi-primary-600: #16a34a;
}

Default values come straight from Tailwind's own default ramps (oklch), so there are no hand-typed hex values to drift.

Dependencies

  • No LoomiUI package dependencies.