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

@epa-datos/ui

v0.1.0

Published

React + Tailwind dashboard component library built on Base UI, published as source so it stays fully readable and themeable in the projects that consume it.

Readme

@epa-datos/ui

React + Tailwind dashboard components built on Base UI, published as source (not a bundle) so the components stay fully readable and themeable in the projects that install them.

There's no barrel index — each file is imported directly, the same way it's imported inside this repo:

import { Button } from "@epa-datos/ui/components/ui/button"
import { Badge } from "@epa-datos/ui/components/ui/badge"
import { Heatmap } from "@epa-datos/ui/components/epa/heatmap"
import { cn } from "@epa-datos/ui/lib/utils"

Install

npm install @epa-datos/ui

react/react-dom ^19 are peer dependencies — everything else the components need (Base UI, Recharts, date-fns, lucide-react, etc.) installs automatically.

Set up styles

Tailwind v4 project required. In your global stylesheet:

@import "tailwindcss";
@import "@epa-datos/ui/styles/tokens.css";

That one import brings in everything the components rely on: the semantic color tokens (--primary, --success, --warning, --info, --chart-1..10, etc.) in light and dark, the dark:/short: custom variants, and the animation/data-state utilities components use for open/close transitions. Override any token by redeclaring it after the import — see Theming below.

Your project also needs to supply two font variables the components inherit rather than hardcode:

// wherever you load fonts (e.g. app/layout.tsx in Next.js)
const sans = YourSansFont({ variable: "--font-sans" })
const mono = YourMonoFont({ variable: "--font-mono" }) // optional, for code/tabular content

Global providers

Mount these once near the root of your app — components assume they exist, the same way they do in this repo's own app/layout.tsx:

import { ThemeProvider } from "next-themes"
import { TooltipProvider } from "@epa-datos/ui/components/ui/tooltip"
import { Toaster } from "@epa-datos/ui/components/ui/toast"

export default function RootLayout({ children }) {
  return (
    <ThemeProvider attribute="class" defaultTheme="light">
      <TooltipProvider>
        {children}
        <Toaster />
      </TooltipProvider>
    </ThemeProvider>
  )
}

Theming

All colors are OKLCH CSS variables — never hardcoded in component source — so re-theming means overriding variables, not editing component files:

@import "tailwindcss";
@import "@epa-datos/ui/styles/tokens.css";

:root {
  --primary: oklch(0.55 0.2 250);
}
.dark {
  --primary: oklch(0.65 0.2 250);
}

Browsing components

This repo is also the showcase — every component and its variants are demoed in components/showcase/demos/*. Clone the repo and run pnpm dev to browse them interactively, or read the source directly under components/ui/ and components/epa/.

Conventions

Full component-selection guidance ("which component fits this request"), styling rules, and the reasoning behind the design tokens live in AGENTS.md — written for both human contributors and coding agents working in this repo.

Contributing / local development

pnpm install
pnpm dev      # showcase app at localhost:3000
pnpm build:lib  # builds the publishable package into dist/

Component and design-token changes are made here, in epa-ui, not in projects that depend on the package — see AGENTS.md for the full editing conventions.

License

MIT