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

@wulperstd/renderer-react

v1.0.0

Published

DOM-free React element renderer for the block editor's document JSON, sharing renderer-core's node/mark rules with renderer-html.

Readme

@wulperstd/renderer-react

DOM-free React element renderer for the block editor's document JSON. Shares @wulperstd/renderer-core's node/mark rules with @wulperstd/renderer-html, so both renderers agree on tags, attributes, and safety gating from one table instead of two independently maintained copies.

See openspec/changes/renderer-react/design.md and openspec/changes/renderer-react/specs/renderer-react-output/spec.md for the full design rationale.

Public API

import {
  renderToReact,
  renderToReactWithDiagnostics,
  DocumentRenderer,
} from '@wulperstd/renderer-react';

const element = renderToReact(doc, {
  nodeMapping: { codeBlock: ({ renderDefault, node }) => renderDefault() },
  markMapping: {},
  unhandledNode: ({ kind, type }) => null,
  onDiagnostic: (record) => console.warn(record),
});

Guarantees

  • Produces a React element tree, never an HTML string, and never uses dangerouslySetInnerHTML.
  • The default (no-override) tree calls no React hook, so it renders identically under renderToStaticMarkup, client-side rendering, and React Server Components.
  • Every safety-relevant attribute (href schemes, color, block-id) is revalidated at render time via @wulperstd/renderer-core's shared predicates, regardless of prior validation.
  • react-dom is a devDependency only, used by this package's own tests and by any consumer's own render call — never imported from src.

Bundle size

The renderer is tree-shakeable: @wulperstd/schema, @wulperstd/renderer-core and this package declare "sideEffects": false, and the renderer only imports schema predicates and constants. A client bundle that uses renderToReact therefore does not include prosemirror-model (about 33 kB minified, 9 kB gzip for the whole renderer chain, excluding React).

validate, validateReport and blockSchema from @wulperstd/schema do need prosemirror-model. Validate on the server (a route loader, an API handler or a Server Component) and pass the validated JSON to the client renderer. test/bundle-size.test.ts fails if prosemirror-model reaches the renderer's client bundle.