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-angular

v0.2.1

Published

The official Tyler Forge™ rich text editor adapter library for Angular.

Readme

@tylertech/forge-rich-text-editor-angular

The official Tyler Forge™ rich text editor adapter library for Angular.

This package provides Angular proxy components and modules for the custom elements in @tylertech/forge-rich-text-editor. It is kept separate from @tylertech/forge-angular so that consumers who do not need an editor never take on TipTap.

Installation

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

Usage

Import ForgeRteModule to get every editor element, or import the individual modules you need.

import { ForgeRteModule } from '@tylertech/forge-rich-text-editor-angular';

@NgModule({
  imports: [ForgeRteModule]
})
export class AppModule {}
<forge-rich-text-editor [maxLength]="500" (change)="onChange($event)">
  <forge-rte-standard-tools></forge-rte-standard-tools>
</forge-rich-text-editor>

Importing a module registers its underlying custom element in the module constructor.

Development

Everything under src/lib and src/public-api.ts is generated from the editor package's custom-elements.json and is overwritten on every build — do not edit it by hand. The generation logic lives in @tylertech/forge-adapter-codegen, which is shared with the React adapter and is the migration path for the hand-maintained adapters; scripts/generate-proxies.mjs here is config only.

pnpm build   # regenerate the proxies, then build the library with ng-packagr

Under the hood it runs the shared @tylertech/forge-schematics:custom-elements schematic twice, because the schematic takes a single importPath while the editor package ships two barrels: the four core elements come from the package root and the forge-rte-* features come from ./features. The split is derived from the manifest so the two passes cannot drift.

It then writes the per-directory index.ts barrels, src/public-api.ts and the aggregate ForgeRteModule, none of which the schematic emits. That gap is worth knowing about: the rich text editor proxies in @tylertech/forge-extended-angular are generated but have no barrels and are absent from its public-api.ts, so they are unreachable to consumers.

Dev harness

pnpm dev   # build, then serve a scratch page at localhost:3462

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

Note that forge-rich-text-editor takes content as an HTML string, while forge-rich-text-renderer takes ProseMirror JSON — the shape the editor's change event emits. They are deliberately different formats.