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

@brain-bbqs/ui

v0.1.1

Published

The shared page shell of the BBQS companion web apps: theme tokens and toggle, header account menu, brand watermarks and footer, human-subjects gate, dropzone, and typed element lookups. Plain DOM, no framework.

Readme

@brain-bbqs/ui

The page shell the three BBQS companion apps draw the same way: the theme palette and light/dark toggle, the header's EMBER account menu, the BBQS watermark and the footer bar with its version stamp and brand marks, the human-subjects gate, the dropzone, and the typed element lookups that back them. Plain DOM and CSS; no framework.

npm install @brain-bbqs/ui

Styles

/* src/style.css */
@import "@brain-bbqs/ui/styles/index.css"; /* tokens + base + shell + components */
/* ...the app's own rules, which may override any token: */
:root {
  --accent: #0e7490;
}

An app that lays out <body> its own way (encoding-helper) imports tokens.css, shell.css and components.css individually and skips base.css. The shared rules select on classes only; the apps keep their ids. Two class names are new and replace id selectors the apps had: .oauth-signin-btn on the sign-in button, .footer-brand-link / .footer-brand-logo on the footer marks (con-brand-link and talmo-brand-link before).

Markup

Each piece exists twice, by design: as a reference fragment under html/ to paste into index.html (keeping the elements test that reads the real page), and as a DOM builder that produces the identical structure at boot. The unit tests assert the two agree.

| Fragment | Builder | | --------------------------------- | ---------------------------- | | html/theme-toggle.html | buildThemeToggle() | | html/account-menu.html | buildAccountMenu() | | html/brand-watermark.html | buildBrandWatermark() | | html/page-footer.html | buildPageFooter() | | html/human-subjects-banner.html | buildHumanSubjectsBanner() | | html/dropzone.html | buildDropzone() |

Behaviour

import {
  getShellElements,
  initThemeToggle,
  renderAuthState,
  renderIdentity,
  bindAccountMenu,
  renderVersion,
} from "@brain-bbqs/ui";

declare const __APP_VERSION__: string;
const shell = getShellElements(); // or getShellElements({ themeToggle: "theme-toggle", ... })

initThemeToggle(shell.themeToggle, { storageKey: THEME_KEY });
renderVersion(shell.versionIndicator, __APP_VERSION__);

if (shell.account) {
  bindAccountMenu(shell.account, { onSignIn: () => void oauth.startLogin(), onSignOut: signOut });
  renderAuthState(shell.account, isSignedIn());
  void fetchArchiveUser(cfg).then((user) => renderIdentity(shell.account!, user));
}

createHumanSubjectsGate owns the confirmed-per-dataset set both upload tools kept in main.ts; bindDropzone owns the dragover class, the click-to-browse plumbing and the window-level guard, leaving what a drop means to the app. h, button, svgEl, escapeHtml and copyToClipboard are encoding-helper's DOM helpers, unchanged.

Storybook

npm run storybook here shows every piece in both themes; the stories are what Chromatic snapshots for this package.