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

@guidoginesi/pow-ui

v0.3.7

Published

POW Design System — tokens, theme y componentes compartidos entre apps POW.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

guidoginesiguidoginesi

Keywords

Readme

@guidoginesi/pow-ui — POW Design System

Sistema de diseño compartido entre apps POW. Light mode, marca fija: tinta #1A1D23 (primary) + naranja #FE722B (brand/accent). Construido sobre Tailwind v4 + Radix + CVA. Sin dependencias de ninguna app — portable.

  • Reglas y patrones: GUIDELINES.md — color, densidad, cuándo usar Tabs / SegmentedControl / TabNav, Sheet vs Dialog, KPIs, gráficos, etc.
  • Migrar una app vieja al DS: MIGRATION-PLAYBOOK.md — proceso con sub-agentes, checklist de 9 criterios, template de prompt.

Instalar

Paquete público en el registry npm. Sin token, sin configuración:

npm i @guidoginesi/pow-ui

Setup en tu app

El paquete trae los componentes; necesitás el entorno alrededor.

Tokens / theme

En tu CSS global, después de Tailwind:

@import "tailwindcss";
@import "@guidoginesi/pow-ui/theme.css";

Esto te da todos los tokens (bg-primary, text-muted-foreground, bg-brand, bg-success-subtle, …), la escala tipográfica (type-display … type-micro), .card, .nums-tabular y los tokens --z-* / --duration-*.

El html { font-size } y el body no vienen en el theme — son shell de cada app; definilos vos.

Componentes

import { Button }  from "@guidoginesi/pow-ui/components/ui/button";
import { Stat }    from "@guidoginesi/pow-ui/components/ui/stat";
import { BarList } from "@guidoginesi/pow-ui/components/ui/bar-list";

Con Next.js, transpilá el paquete (trae .tsx sin compilar):

// next.config.ts
transpilePackages: ["@guidoginesi/pow-ui"],

Peer deps

Instalá las que usás (ver package.json): class-variance-authority, clsx, tailwind-merge, lucide-react, date-fns, cmdk, sonner y los @radix-ui/*.

Fuente de marca (opcional)

Los títulos usan var(--font-display) → --font-helvetica-now. Cargala con next/font/local y ponela en <html className={helveticaNow.variable}>. Sin esto, los títulos caen al stack del sistema (funciona, sin la marca).

Publicar una versión nueva (mantenedor)

npm login          # una vez, con la cuenta dueña del scope @guidoginesi
# bump de versión en package.json, luego:
npm publish        # publishConfig.access = public → npm público

Governance

  1. Nunca colores crudos. bg-blue-600 ❌ → bg-primary ✅.
  2. Un primary (tinta) por vista; brand (naranja) es acento, no acción.
  3. Estados con tokens semánticos (success/warning/danger + -subtle).
  4. Montos con nums-tabular.
  5. Radius vía rounded-[var(--radius)].

Detalle completo en GUIDELINES.md.