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

@bleeb/ui

v0.1.1

Published

Bleeb design system — brand atoms, Neon components, shadcn/ui, tokens and styles.

Vulnerabilities

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

Links

Git

Maintainers

bleebbleeb

Keywords

Readme

@bleeb/ui

Design system di Bleeb — atomi di brand, componenti Neon, set completo shadcn/ui, token e CSS pronto.

Versione 0.1.0. Pacchetto pubblico MIT del design system Bleeb.

Installazione

npm install @bleeb/ui
# peer deps
npm install react react-dom tailwindcss

Oppure da git (senza pubblicare):

# bun / pnpm supportano i subpath
bun add @bleeb/ui@github:<org>/<repo>#path:packages/ui

Setup

1. CSS

Importa il foglio di stile una sola volta nell'entry dell'app:

// src/main.tsx  oppure  src/routes/__root.tsx
import "@bleeb/ui/styles.css";

Contiene reset, font, CSS variables di Bleeb e i blocchi @theme di Tailwind v4.

2. Tailwind v4

Se la tua app non ha già Tailwind configurato:

/* app.css */
@import "tailwindcss";
@import "@bleeb/ui/styles.css";

Tutti i token (--bg, --cyan, --surface-1, ecc.) e le utility (bg-bleeb-cyan, text-foreground...) diventano disponibili automaticamente.

2b. Fonts

Il pacchetto non bundle-a font: vanno caricati lato app. Tre opzioni, scegline una.

A. Self-host via @fontsource (consigliato) — i font sono dichiarati come optionalDependencies, installali con:

npm i @fontsource/inter @fontsource/space-grotesk @fontsource/jetbrains-mono

Poi nell'entry:

import "@fontsource/inter/400.css";
import "@fontsource/inter/500.css";
import "@fontsource/inter/600.css";
import "@fontsource/space-grotesk/400.css";
import "@fontsource/space-grotesk/500.css";
import "@fontsource/space-grotesk/600.css";
import "@fontsource/space-grotesk/700.css";
import "@fontsource/jetbrains-mono/400.css";
import "@fontsource/jetbrains-mono/500.css";
import "@bleeb/ui/styles.css";

B. Google Fonts CDN — nell'<head>:

<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600&family=Space+Grotesk:wght@400;500;600;700&family=JetBrains+Mono:wght@400;500&display=swap">

C. File brand — i .woff2 ufficiali stanno in public/brand/fonts/ della repo. Scarica fonts.css + i .woff2, mettili sotto public/ della tua app e:

@import url("/brand/fonts/fonts.css");

Famiglie / pesi attesi dai token (--font-display, --font-sans, --font-mono):

| Token | Famiglia | Pesi | |---|---|---| | --font-display | Space Grotesk | 400, 500, 600, 700 | | --font-sans | Inter | 400, 500, 600 | | --font-mono | JetBrains Mono | 400, 500 |

3. Token in JS

import { colors, accents, gradients, payoffs } from "@bleeb/ui/tokens";
import { bleebTheme } from "@bleeb/ui/tailwind-preset";

Import

Entry granulari (consigliati per il tree-shaking):

import { NeonButton, NeonInput } from "@bleeb/ui/neon";
import { BleebLogo, BleebPayoff } from "@bleeb/ui/brand";
import { Button, Card, Dialog } from "@bleeb/ui/ui";
import { colors, voicePillars } from "@bleeb/ui/tokens";

Entry root (più comodo, leggermente più grosso):

import { NeonButton, BleebLogo, colors } from "@bleeb/ui";

Cosa c'è dentro

| Entry | Contenuto | |---|---| | @bleeb/ui/brand | BleebLogo, BleebSymbol*, BleebWordmark, BleebLockups, BleebPayoff, BleebAvatar, BleebBadge, BleebTag, BleebKbd, BleebDivider, BleebMetric, BleebCallout, BleebCodeBlock, useLogoMotion | | @bleeb/ui/neon | NeonButton, NeonInput, NeonTextarea, NeonCheckbox, NeonSwitch, NeonRadioGroup, NeonSlider | | @bleeb/ui/ui | shadcn/ui completo (45 componenti) + cn | | @bleeb/ui/tokens | colors, accents, gradients, radii, durations, easings, type, payoffs, voicePillars, toneAttributes, doExamples | | @bleeb/ui/styles.css | CSS globali (variables + @theme) | | @bleeb/ui/tailwind-preset | bleebTheme (oggetto token) + tailwindV3Preset (legacy) |

Build / dev / test / publish

Tutti gli script funzionano sia con pnpm (dal root del monorepo) sia con npm (dentro packages/ui/).

Build

# pnpm
pnpm --filter @bleeb/ui build

# npm
cd packages/ui && npm install && npm run build

Watch

pnpm --filter @bleeb/ui dev
# oppure
cd packages/ui && npm run dev

Test / typecheck

test esegue tsc --noEmit. Sostituiscilo con vitest run se aggiungi test unitari.

pnpm --filter @bleeb/ui test
# oppure
cd packages/ui && npm test

Dry-run publish

pnpm --filter @bleeb/ui publish:dry
# oppure
cd packages/ui && npm run publish:dry

Publish su npm

npm login                                              # una tantum
pnpm --filter @bleeb/ui release:patch                  # bump + publish
# oppure
cd packages/ui && npm run release:patch

# manuale
cd packages/ui
npm version <patch|minor|major>
npm publish --access public

Lo script prepack ricostruisce dist/ prima della pubblicazione, quindi non serve buildare a mano.

Alias dal root della repo (bun)

bun run ui:build
bun run ui:test
bun run ui:publish:dry
bun run ui:publish
bun run ui:release:patch

Il sito brand book della repo padre non viene toccato dal build del pacchetto.

Peer deps

react >=18, react-dom >=18, tailwindcss >=4. Tutto il resto (Radix, lucide, framer-motion, recharts, ecc.) è gestito come dependencies del pacchetto.

Link

  • Sito: https://bleeb.dev
  • Issues: https://github.com/bleeb/bleeb/issues