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

@usereq/bundlehive

v0.1.1

Published

Author standalone, embeddable React components — they mount as Shadow-DOM custom elements with isolated CSS.

Readme

@usereq/bundlehive

The runtime + authoring API for BundleHive — build a standalone, embeddable React component that mounts onto any website as a Shadow-DOM custom element with isolated CSS (Tailwind v4 included).

npm install @usereq/bundlehive react react-dom

Usage

// widget.tsx
import { useWidget } from "@usereq/bundlehive";

export function Widget() {
  const { config } = useWidget<{ title?: string }>();
  return <div className="rounded-xl bg-white p-4 shadow">{config.title ?? "Hello"}</div>;
}
// embed.ts — importing this registers <acme-widget>
import { defineWidget } from "@usereq/bundlehive";
import styles from "./styles.css?inline";
import { Widget } from "./widget";

export default defineWidget(Widget, {
  tag: "acme-widget",
  styles,
  observedAttributes: ["title"],
});

Build with @usereq/bundlehive-cli, then:

<acme-widget title="Hi"></acme-widget>
<script src="https://unpkg.com/@acme/widget" async></script>

Exports

| Export | Purpose | | --- | --- | | defineWidget(Component, options) | Turn a React component into a Shadow-DOM custom element | | useWidget<Config>() | Read runtime config + host handle inside the component | | useWidgetCommands(cmd => …) | Handle imperative commands (open/close/…) from the loader | | Portal | Overlays (dialogs/popovers) scoped to the shadow root | | createLoader(name, def, opts?) | Install a command-queue loader (Intercom-style) | | onDomReady(fn) | DOM-ready guard for self-injecting widgets |

What it handles for you

  • Shadow-DOM mount with the React root inside the shadow boundary.
  • Tailwind v4 in shadow DOM — the runtime hoists @property rules and rewrites :root:host, delivering styles via a shared constructable stylesheet. (Tailwind v4 otherwise renders unstyled inside shadow roots.)
  • Runtime config from element attributes or the loader API — one bundle, all tenants.
  • Three embed modes: placed element, auto-inject launcher, command-queue loader.

Client render only — no SSR. See the repo for the full guide, and llms.txt for an agent-readable reference.

License

MIT