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

@openeditor/custom-block

v0.0.49

Published

Use this package to add trusted, build-time custom blocks to OpenEditor without adding a ProseMirror node type for each block.

Readme

@openeditor/custom-block

Use this package to add trusted, build-time custom blocks to OpenEditor without adding a ProseMirror node type for each block.

OpenEditor stores every installed block in one atomic customBlock node. A block package owns its data parser, version migration, static output, and asset references. OpenEditor owns the envelope, registry, editor and Viewer lifecycle, missing-block fallback, and safe HTML serialization.

import {
  createOpenEditorCustomBlockRegistry,
  defineOpenEditorCustomBlock,
} from "@openeditor/custom-block";

type CardData = { title: string };

export const card = defineOpenEditorCustomBlock<CardData>({
  id: "acme.card",
  label: "Card",
  version: 1,
  createData: () => ({ title: "Untitled" }),
  parseData: (value) => {
    if (!value || typeof value !== "object" || !("title" in value))
      throw new Error("Card title is required.");
    if (typeof value.title !== "string")
      throw new Error("Card title must be a string.");
    return { title: value.title };
  },
  toHtml: ({ data }) => ({ tag: "article", children: [data.title] }),
  toText: ({ data }) => data.title,
});

export const registry = createOpenEditorCustomBlockRegistry([card]);

The parser is the authoritative data contract. Use the same registry in the browser, backend, publisher, migration, and exporters. This prevents validation rules from drifting across environments.

Import React editor adapters from @openeditor/custom-block/editor. Import published Viewer adapters from @openeditor/custom-block/viewer. The Viewer entry point does not import Tiptap or editor code.

Use migrate only while a stored data version is active. The function must return the complete next envelope and increase the version. A final application release can remove the migration after all stored documents use the current version.

Use assets to return host-managed asset IDs and JSON paths. The host authorizes and resolves these opaque IDs. Block packages do not receive storage clients or credentials.

Use conformOpenEditorCustomBlock in each block package test. It verifies initial data, parsing, and safe static output.