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

@tydavidson/design-system

v1.2.9

Published

Float Design System with email components and theme system

Readme

Float Design System

A modern React design system with comprehensive theming, component library, and email components.

Quick Start

npm install @tydavidson/design-system

Documentation

📚 Setup Guide: docs/setup-guide.md - Complete installation and configuration guide

🔧 Troubleshooting: docs/troubleshooting.md - Quick fixes for common issues

🎨 Theme Usage: docs/theme-usage.md - Detailed theme system documentation

Features

  • Modern React Components - Built with TypeScript and React 18+
  • Theme System - Light/dark mode with CSS variables
  • Next.js Compatible - Works with App Router and Pages Router
  • Email Components - Responsive email templates
  • Tabler Icons - Consistent icon library
  • Tailwind CSS - Utility-first styling
  • TypeScript - Full type safety

Basic Usage

import { ThemeProvider, useTheme, ThemeToggle } from '@tydavidson/design-system/themes';
import { Button, Card, CardContent, CardHeader, CardTitle } from '@tydavidson/design-system';
import '@tydavidson/design-system/themes/theme.css';

function App() {
  return (
    <ThemeProvider>
      <Card>
        <CardHeader>
          <CardTitle>Welcome</CardTitle>
        </CardHeader>
        <CardContent>
          <Button>Get Started</Button>
          <ThemeToggle />
        </CardContent>
      </Card>
    </ThemeProvider>
  );
}

Required Dependencies

npm install react react-dom next-themes @tabler/icons-react

Development Commands

This project uses mise for task management. Below are the available commands:

Build

mise build

Build the project.

LLM Tasks

The following LLM-powered development tasks are available:

mise llm_bundle

LLM-powered bundling task.

mise llm_code_review

Run an LLM-powered code review.

mise llm_copy

LLM copy task.

mise llm_github_issues

LLM task for GitHub issues management.

mise llm_missing_tests

Identify missing tests using LLM.

mise llm_readme

Generate or update README using LLM.

Running Tasks

You can run any task using either:

mise run <task_name>
# or the shorthand:
mise <task_name>

To see all available tasks:

mise tasks

Design System

This project uses a comprehensive design system with semantic CSS variables and component-specific styling patterns.

CSS Variable Naming Conventions

We use two complementary naming patterns for our CSS variables:

1. Global Semantic Variables

For application-level styling, we use semantic variables organized by property type:

/* Pattern: --{property}-{context}-{hierarchy} */
--bg-primary              /* Primary background */
--bg-secondary            /* Secondary background */
--bg-brand-primary        /* Brand context, primary level */
--text-primary            /* Primary text color */
--text-error-primary      /* Error context, primary level */
--border-primary          /* Primary border color */
--border-brand            /* Brand context border */

Usage in application code:

<div className="bg-bg-primary text-text-primary border-border-secondary">
  Application content
</div>

2. Component-Specific Variables

For reusable components, we use component-first naming:

/* Pattern: --{component}-{property}-{variant}-{state} */
--button-bg-primary           /* Button background, primary variant */
--button-bg-primary-hover     /* Button background, primary variant, hover state */
--input-border-focus          /* Input border, focus state */
--dropdown-item-bg-brand-hover /* Dropdown item background, brand variant, hover state */

Usage in component libraries:

<button className="bg-[var(--button-bg-primary)] hover:bg-[var(--button-bg-primary-hover)]">
  Click me
</button>

Key Benefits

  • 🎯 Component Grouping: All variables for a component are grouped together (e.g., --button-*)
  • ⚡ Developer Experience: Autocomplete shows all related variables when typing component name
  • 🔄 Third-party Override: Can override third-party library variables with same names
  • 📐 Semantic Consistency: Aligns with global design system patterns
  • 🎨 Maintainability: Clear organization and naming conventions

Examples by Component

Button Variables:

--button-bg-primary, --button-bg-secondary, --button-bg-destructive
--button-text-primary, --button-text-link, --button-text-ghost
--button-border-outline, --button-icon-size-sm

Input Variables:

--input-bg, --input-bg-disabled
--input-text, --input-text-placeholder
--input-border, --input-border-hover, --input-border-focus

Dropdown Variables:

--dropdown-bg, --dropdown-text, --dropdown-border
--dropdown-item-bg-hover, --dropdown-item-text-brand-hover
--dropdown-separator-bg

Documentation

For detailed implementation guidelines, migration instructions, and complete variable references, see:

Quick Start

  1. For application styling: Use semantic utilities like bg-bg-primary, text-text-secondary
  2. For component styling: Use component variables like --button-bg-primary, --input-border-focus
  3. Adding new components: Follow the --{component}-{property}-{variant} pattern
  4. Dark mode: All variables automatically support light/dark themes

This design system enables consistent, maintainable, and scalable styling across the entire application while providing excellent developer experience.