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

@techrox/page-studio-renderer

v1.0.0

Published

SSR-safe React renderer for displaying saved Puck JSON from @techrox/page-studio on a public page. Small footprint, no editor dependencies.

Readme

@techrox/page-studio-renderer

Server-safe renderer for @techrox/page-studio Puck output.

Use this on public pages to display whatever your admin saved in the editor. Renders to clean HTML in SSR, so search engines + users see the content immediately — no hydration flash.

pnpm add @techrox/page-studio-renderer @techrox/page-studio-blocks
pnpm add @puckeditor/core                          # peer

Usage

Next.js App Router (server component):

import { PageStudioRender } from '@techrox/page-studio-renderer';
import { fetchPage } from '@/lib/cms';

export default async function HomePage() {
  const data = await fetchPage('page.home');  // your CMS read
  return (
    <PageStudioRender
      data={data}
      studio={{ /* same shape as the editor */ }}
      fallback={<StaticDefault />}
    />
  );
}

If data is empty or missing, fallback is rendered instead — so the public site can always ship a sensible default when the CMS has no override yet.

Props

| Prop | Type | Notes | |---|---|---| | data | PuckData \| null | The JSON your editor saved. Empty content arrays render the fallback. | | config | PuckConfig | Optional override; default uses createPuckConfig(). | | fallback | ReactNode | Rendered when data is missing/empty. Defaults to null. | | studio | StudioValue | Forwarded to <PageStudioProvider> — same shape as the editor's studio prop. |

The renderer must see the same studio value as the editor so blocks see consistent service catalogues, Link components, and site metadata across edit + view.

What this package wraps

<Render> from @puckeditor/core, plus <PageStudioProvider> from @techrox/page-studio-blocks. That's it.

You could write the same five lines yourself; this package exists so server-only consumers don't have to add the editor as an indirect dependency.

License

MIT.