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

@lindle/linoardo

v1.0.60

Published

All components are server components, if possible. If not, mark file as "use client" Components working with forms must be compatible with react-hook-form.

Readme

instructions for codex

All components are server components, if possible. If not, mark file as "use client" Components working with forms must be compatible with react-hook-form.

Linoardo

Linoardo is a React UI component library. It is built on Tailwind CSS, includes core building blocks (Button, Input, Menu, Dialog, etc.), and lets you easily override the color palette via CSS variables.

Installation

npm i @lindle/linoardo
# or
pnpm add @lindle/linoardo
# or
yarn add @lindle/linoardo

Usage

  1. Import the library styles.
  2. Import the components you want to use.
import '@lindle/linoardo/styles.css';
import { Button } from '@lindle/linoardo';

export default function App() {
  return <Button color='primary'>Action</Button>;
}

Dark mode

Linoardo respects the user's system preference (prefers-color-scheme) by default — no configuration needed.

Behaviour overview

| Situation | Result | |---|---| | No class set, system is light | light mode | | No class set, system is dark | dark mode (automatic) | | .dark on any ancestor | force dark, regardless of system setting | | .light on any ancestor | force light, regardless of system setting |

Forcing a specific theme

Add .dark or .light to the <html> element (or any wrapper that contains Linoardo components):

<!-- force dark -->
<html class="dark">

<!-- force light -->
<html class="light">

In React you can toggle it programmatically:

function setTheme(theme: 'dark' | 'light' | 'system') {
  const root = document.documentElement;
  root.classList.remove('dark', 'light');
  if (theme !== 'system') root.classList.add(theme);
}

Persisting the user's choice

// read saved preference on mount
const saved = localStorage.getItem('theme') as 'dark' | 'light' | 'system' | null;
if (saved && saved !== 'system') {
  document.documentElement.classList.add(saved);
}

// save on change
function handleThemeChange(theme: 'dark' | 'light' | 'system') {
  localStorage.setItem('theme', theme);
  setTheme(theme);
}

Reacting to system changes at runtime

const mq = window.matchMedia('(prefers-color-scheme: dark)');

mq.addEventListener('change', (e) => {
  const saved = localStorage.getItem('theme');
  // only follow system if the user hasn't pinned a theme
  if (!saved || saved === 'system') {
    document.documentElement.classList.toggle('dark', e.matches);
  }
});

Color palette (CSS variables)

Palette colors are controlled by CSS variables. Default values:

  • --color-primary
  • --color-neutral
  • --color-info
  • --color-success
  • --color-warning
  • --color-danger
  • --color-surface
  • --color-bw

You can override them globally:

:root {
  --color-primary: #0ea5e9;
  --color-neutral: #4b5563;
  --color-info: #0ea5e9;
  --color-success: #10b981;
  --color-warning: #f59e0b;
  --color-danger: #ef4444;
  --color-surface: #ffffff;
  --color-bw: #000000;
}

If you want to scope the color locally, set it on a wrapper element:

.app-theme {
  --color-primary: #22c55e;
  --color-info: #38bdf8;
  --color-danger: #f97316;
}

Development

npm run dev        # Storybook on port 6006
npm run build      # JS + CSS production build
npm run lint       # ESLint
npx vitest         # Storybook interaction tests (headless Chromium)

docker build --no-cache -t linoardo-storybook:latest .