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

@tylertech/forge-rich-text-editor

v0.3.0

Published

Tyler Forge™ rich text editor Web Components

Readme

Tyler Forge™ Rich Text Editor

A rich text editor Web Component library for Tyler Forge™, built on Tiptap.

Installation

npm install @tylertech/forge-rich-text-editor

@tylertech/forge is a peer dependency and must be installed alongside this package.

Usage

import '@tylertech/forge-rich-text-editor';
<forge-rich-text-editor>
  <forge-rte-standard-tools></forge-rte-standard-tools>
</forge-rich-text-editor>

Development

pnpm dev     # serve a scratch page at localhost:3460
pnpm test    # run the suite in a real browser
pnpm build   # rollup ESM, custom elements manifest and types

src/dev is a page for looking at the components in a real browser. It is never published, and it imports the built esm/ output rather than source, so it exercises the same artifact a consumer gets.

forge-rich-text-editor takes content as an HTML string or a ProseMirror document, while forge-rich-text-renderer takes only a document — the shape the editor's change event emits.

To give the renderer HTML, convert it first with toRichTextDocument(html). It sanitizes the HTML and returns the document an editor with forge-rte-standard-tools would produce from it. Pass features to match a different editor, for example toRichTextDocument(html, [...RICH_TEXT_STANDARD_FEATURES, 'link']). RICH_TEXT_FEATURES lists every feature name, and unknown names are skipped with a warning. It parses with DOMParser, so it needs a browser or a DOM shim such as jsdom or happy-dom.

Document input is stricter than HTML input: ProseMirror rejects a mark it has no extension for and discards the whole document, whereas HTML parsing drops the unknown formatting and keeps the text. Slot the features providing the marks your content uses.

When a document is rejected the editor dispatches its error event with { context: 'Invalid document content', error }, where the message names the offending mark, and logs the same through console.error. The content is still discarded — this only reports it, since TipTap alone logs a warning that an application cannot react to. HTML input is deliberately not reported, because dropping unsupported formatting there is expected behaviour rather than a fault.

License

Apache-2.0