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

@lyra-ds/styles

v0.5.0

Published

Lyra DS — CSS-first design tokens + component styles (211 tokens, 78 components), zero JS.

Readme

@lyra-ds/styles

CSS-first design tokens and component styles for the Lyra Design System — 211 tokens and 78 components, zero JavaScript. The look of every Lyra component lives in .lyra-* classes, so the same CSS is reusable across any framework.

Install

npm install @lyra-ds/styles

Usage

A single import wires up all tokens and every component:

import '@lyra-ds/styles';

or, from a stylesheet:

@import '@lyra-ds/styles';

Both resolve to styles.css, which @imports the 7 token layers followed by the 11 component layers in the canonical handoff order. The literal subpath also works if you prefer to be explicit:

import '@lyra-ds/styles/styles.css';

With no data-theme or data-brand attribute set, importing the entry yields the baseline light appearance.

Individual token files

Need only a slice? Each token file is reachable through the ./tokens/* subpath:

@import '@lyra-ds/styles/tokens/colors.css';
@import '@lyra-ds/styles/tokens/spacing.css';

There are no per-component subpaths — import the full entry for component styles.

White-label brand contract

Re-brand Lyra by defining only 4 input tokens on a [data-brand] scope. The entire accent group is derived via color-mix(in oklab, …) — no rebuild, and it works in both light and dark.

| Input token | Required? | Default | Purpose | | ------------------ | ------------ | ----------------------- | ------------------------------------------------ | | --brand | required | — | Brand primary color | | --brand-contrast | optional | #FFFFFF | Text/foreground on brand fills (--on-accent) | | --brand-radius | optional | 10px | Overrides --radius-md (default control radius) | | --brand-font | optional | Plus Jakarta Sans stack | Overrides --font-sans + --font-display |

Set data-brand="acme" on your <html> (or any ancestor) and define the brand tokens:

[data-brand='acme'] {
  --brand: #0d9488;
  --brand-radius: 6px;
}
<html data-brand="acme"></html>

The [data-brand] layer is inert until the attribute is present, and every derived accent value (hover, active, soft, focus-ring, link, border) is mixed automatically for both light and dark themes.

Fonts (peer install)

Fonts are not bundled and are never loaded from a runtime CDN. Install them as peers and import the weights you need from your own app — this replaces the CDN request the prototype used.

npm install @fontsource/plus-jakarta-sans @fontsource/jetbrains-mono

Plus Jakarta Sans backs --font-sans / --font-display; JetBrains Mono backs --font-mono. Import every weight the design system uses:

// Plus Jakarta Sans — weights 400–800
import '@fontsource/plus-jakarta-sans/400.css';
import '@fontsource/plus-jakarta-sans/500.css';
import '@fontsource/plus-jakarta-sans/600.css';
import '@fontsource/plus-jakarta-sans/700.css';
import '@fontsource/plus-jakarta-sans/800.css';

// JetBrains Mono — weights 400–600
import '@fontsource/jetbrains-mono/400.css';
import '@fontsource/jetbrains-mono/500.css';
import '@fontsource/jetbrains-mono/600.css';

shadcn/ui compatibility (opt-in)

Apps that mix Lyra with shadcn/ui components can import the opt-in compatibility layer, which maps shadcn's semantic variables onto Lyra tokens. It is never imported by styles.css — import it explicitly, after the entry:

import '@lyra-ds/styles';
import '@lyra-ds/styles/compat-shadcn.css';

License

MIT