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

@nubbin/react

v0.6.0

Published

The React render path for Nubbin: render a compiled artifact against a block registry.

Readme

@nubbin/react

The React render path for Nubbin. It walks a compiled artifact, loads the blocks that artifact names, resolves the data holes it declares, and renders them.

npm install @nubbin/react
import { defineRegistry, Renderer } from "@nubbin/react";

export const registry = defineRegistry({
  Hero: () => import("./blocks/Hero").then((m) => m.Hero),
});

export default async function Page() {
  const artifact = await resolveArtifact(store, slug);
  return <Renderer artifact={artifact} registry={registry} />;
}

Each registry value is an import() the bundler can see, which is what gives one chunk per block; a route resolves only the names its artifact carries, so the hundredth block costs pages that do not use it nothing. A block author types their component as BlockComponent<HeroProps>; the registry stores it with its props erased, because function parameters are contravariant and a shared props type would be assignable from no real component.

Renderer is an async server component. It invokes each block and stamps data-nubbin-node on the element that block returns, which is how the studio maps a node in the tree to a region on the page. A block is therefore a server component returning exactly one root element — a Fragment root or a client reference has no root to stamp, and the renderer throws naming the block rather than wrapping it in an element the consumer's layout did not ask for.

Slot children arrive as props: slots.sections renders to props.sections, an array of elements the block places itself.

<Renderer
  artifact={artifact}
  registry={registry}
  resolveHole={async ({ block, path, spec }) => fetchLiveValue(block, path, spec)}
/>

A hole is a field a block marked as fetched per request or on an interval, which compile deliberately left unfrozen; spec is "request" or { revalidate: n } — exactly what compile wrote. A node with no holes never calls the resolver. A node that declares holes and gets no resolver throws naming the node, rather than rendering a compile-time placeholder to a visitor.

Read the Nubbin documentation for the complete renderer reference. MIT.