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

@t3b/hub-ui

v0.3.0

Published

The3Beez apps' look, built from the3beez-design-system (D-053): its tokens and app components as one stylesheet, its POS set as a second one for a counter, plus the logo. Installed by every app; never copied by hand.

Vulnerabilities

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

Links

Git

Maintainers

dooflietdoofliet

Keywords

Readme

@t3b/hub-ui

The3Beez apps' look, as one package (D-053, WORKFLOWS §12). Its source is the design system, the3beez-design-system (DESIGN.md): css/app.css is generated from the design system's tokens and components (in the order its components.css gives, without the till's parts) and stamped with the version and commit it came from. Every app installs it; a colour, font or component typed into an app is a defect.

npm install @t3b/hub-ui
// app/layout.tsx (Next.js)
import "@t3b/hub-ui/css/app.css";
  • A counter (the till, A-501) also loads the design system's POS set, after app.css: import "@t3b/hub-ui/css/pos.css"; - the sell screen, tiles, ticket, payment, receipt and shift parts. No other app needs it.
  • Fonts load from the Kuwait theme on Shopify's CDN (https://kw.the3beez.com/cdn/shop/t/24/…), as the design system rules; allow that origin in the app's CSP font-src. No font files ship here.
  • Theme: light by default; dark when an ancestor (normally <html>) has data-theme="dark".
  • Direction: logical properties throughout; set dir on <html>.
  • Logo: <span class="brand-mark" role="img" aria-label="The3Beez"></span> — one colour that follows the theme (a mask of brand/logo.svg); brand/logo.png for places without CSS (email).
  • Components are the design system's classes — the app shell (.app, .app-side, .side-list, .app-top, .app-main), .page-head, .section-head, .btn (-primary, -secondary, -ghost, -accent, -danger, -link), .field / .input / .select-wrap / .switch, .card, .stat, .badge (-success, -warning, -danger, -muted), .table-wrap / .table, .tabs, .alert, .kv, .modal, .drawer, .otp … — see DESIGN.md §4 and its sections/ examples. The apps' additions are listed in src/apps.css (not published; built into app.css).

Rebuilding after the design system changes

npm run -w @t3b/hub-ui sync -- "C:\Users\doofl\Claude\Projects\the3beez-design-system"

The script refuses a design system with uncommitted changes (the stamp must name what was built). Then bump the version, run the Hub's tests (they fail if app.css was edited by hand), open a PR, and publish with the hand-run workflow (OWNER-SETUP §N).