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

@eldrajs/rich-text

v0.1.0

Published

Framework-free rendering for Eldra CMS rich text: the document types, plain-text extraction, an escaping HTML serialiser, and embed normalisation.

Readme

@eldrajs/rich-text

Framework-free handling of the rich text the Eldra CMS delivers: a TipTap (ProseMirror) JSON document. Render it to an HTML string, extract its plain text, or build a renderer for your own framework on top of the types and helpers.

pnpm add @eldrajs/rich-text

Render to HTML

import { toHtml } from '@eldrajs/rich-text';

const html = toHtml(entry.data.body);

Every text node and attribute value is escaped. Link hrefs are limited to http, https, mailto, tel and relative paths; image sources to http, https, data:image/ and relative paths; an embed renders only from a host the editor's own normaliser can emit. A script-mode embed (X, Instagram, Pinterest) becomes a link card — static HTML cannot run a provider's widget script, and this package never emits one.

The output is deliberately plain: <p>, <h2>, <ul>, <table> with <thead>/<tbody>, and so on, with no classes. Style it with your own prose styles, or override:

toHtml(doc, {
  nodes: {
    paragraph: { class: 'lead' },
    heading: (node, children, { element }) =>
      element(`h${node.attrs?.level ?? 2}`, { class: 'display' }, children),
    codeBlock: null, // children only, no <pre>
  },
  marks: { bold: 'b' },
});

An override is a tag name, { tag?, class?, style? }, null for children only, or a function (node, children, context) => string. children is already rendered and escaped.

Plain text

import { renderTipTapText } from '@eldrajs/rich-text';

const { text, truncated } = renderTipTapText(doc, { wordCount: 30 });

Building a framework renderer

The Vue renderer in @eldrajs/vue is built on this package: RichTextDocument and friends for the shape, resolveOverride for the override semantics, safeHref / safeImageSrc / isTrustedEmbedSource for the same safety rules, and normalizeEmbedInput for embeds. A React or Svelte renderer would use exactly the same pieces. The contract a wrapper has to satisfy is written in docs/frameworks.md — a wrapper for another framework is welcome.