Angular rich text editor with built-in spellcheck

Why this is unusual

Most Angular rich text editors treat spellcheck as somebody else's job. You get formatting, lists and links, and then you either accept the browser's native checker, which you cannot style, position or control, and which disappears the moment you set contenteditable to a custom implementation, or you bolt on a paid service that sends every keystroke to someone's server.

Sqwig ships the dictionary. A SymSpell engine compiled to WebAssembly runs in a Web Worker beside your editor, checks as the user types, and renders its own underlines and suggestion popover. Nothing is transmitted, so there is no request to fail, no latency to hide, and nothing to put in a DPA.

Install

npm i @sqwig/core @sqwig/angular

Requires Angular 15 or newer: the wrapper is a standalone component, and there is no NgModule.

Then serve the three runtime assets: the WASM engine, its worker, and the dictionary chunks. A bundler cannot inline them because they are fetched at runtime. With the Angular CLI, copy them into public/sqwig/, or publish them straight from node_modules via angular.json (see serving the assets). Full detail in the quickstart.

Basic usage

<sqwig-editor> is a thin, uncontrolled wrapper. It takes a single required options input, the same object createEditor takes, read once at mount.

import { Component, ViewChild } from "@angular/core";
import { SqwigEditorComponent } from "@sqwig/angular";
import { createSpellChecker } from "@sqwig/core";

@Component({
  selector: "app-editor",
  standalone: true,
  imports: [SqwigEditorComponent],
  template: `
    <sqwig-editor [options]="options" (change)="save($event)"></sqwig-editor>
  `,
})
export class EditorComponent {
  // Create ONCE, as a class field. The object is read once, at mount,
  // and the spellchecker owns a Web Worker and a WASM instance.
  readonly options = {
    license: "free",
    spell: createSpellChecker({ assetBaseUrl: "/sqwig/" }),
    placeholder: "Say something…",
  };

  @ViewChild(SqwigEditorComponent) sqwig?: SqwigEditorComponent;

  save(html: string) { /* your persistence */ }
}

Declaring options as a class field is the single most important line on this page. It is created once per component instance, so the spellchecker, with its Worker and WASM engine, is created once. A getter that builds a fresh object would run on every change-detection cycle.

One options input, three outputs

Options do not travel as individual inputs: a per-field @Input() surface would be a hand-maintained mirror of EditorOptions that drifts every time the core adds an option. One object avoids the drift and matches createEditor exactly.

class and style need no inputs at all; Angular puts them on the component's host element natively.

The editor mounts outside the Angular zone, so its keystroke handling and spellcheck passes do not trigger app-wide change detection. Output emissions re-enter the zone, so your bindings update normally under default change detection, and the component also works under zoneless bootstrap.

@ViewChild exposes the editor

The component's public editor field is the complete core Editor instance: not a subset, and not an Angular-flavoured shim. Anything the core can do, you can do.

@ViewChild(SqwigEditorComponent) sqwig?: SqwigEditorComponent;

// later
this.sqwig?.editor?.getHTML();
this.sqwig?.editor?.setHTML("<p>Replaced</p>");
this.sqwig?.editor?.focus();

editor is null before ngAfterViewInit and after destroy. See editor methods and events.

Why there is no ngModel

Deliberately. A two-way bound rich text editor has to reconcile a framework render against a live DOM selection on every keystroke, and the usual result is a cursor that jumps to the end of the document mid-word. A ControlValueAccessor would also imply forms integration, validators, and touched/dirty semantics the wrapper does not honor. Sqwig keeps the document in the editor and hands you HTML through (change).

In practice: hold the HTML wherever you need it for a save button, but do not feed it back in. To replace content programmatically, call setHTML on the exposed editor. One content model, same as the React and Vue wrappers.

Serving the assets with the Angular CLI

Either route works; pick one.

Copy into public/ (or your project's static assets folder) and point at it with a root-relative path:

cp -r node_modules/@sqwig/core/dist public/sqwig

Or publish straight from node_modules so the files stay current with the installed package:

"assets": [
  { "glob": "spell_wasm_bg.wasm", "input": "node_modules/@sqwig/core/dist", "output": "sqwig" },
  { "glob": "spell.worker.js",    "input": "node_modules/@sqwig/core/dist", "output": "sqwig" },
  { "glob": "dict/*",             "input": "node_modules/@sqwig/core/dist", "output": "sqwig" }
]

Do not import the worker or the .wasm. The build would try to fingerprint and rewrite them, and the runtime fetch then misses. They are served files, not module graph members.

Angular Universal and server rendering

The editor needs a real DOM, a Web Worker and WebAssembly, so it is client-only. The component's template is an empty host element, and it mounts the editor in ngAfterViewInit, which does not run during server rendering. No platform guard needed.

Common pitfalls

Options built by a getter

get options() { return { license: "free", spell: createSpellChecker() }; } runs on every change-detection cycle and rebuilds the object, spellchecker, Worker and all. Declare it once, as a class field, as above.

Changing options and nothing happening

The options object is read once, at mount. Mutating it later, or binding a new object, will not re-initialise the editor. Use the exposed editor for runtime changes, or force a remount with *ngIf if you genuinely need fresh options.

Underlines never appear

The editor mounted but the assets 404'd. Check the Network panel for spell.worker.js, spell_wasm_bg.wasm and dict/. The editor deliberately keeps working without them, so this fails quietly.

Reading the editor too early

this.sqwig?.editor is null until ngAfterViewInit has run. Read it from lifecycle hooks at or after that point, or from event handlers, not from the constructor or ngOnInit.

Where to go next

• Quickstart: installation, assets, the license option
• createEditor options: the full table
• Styling and theming: CSS custom properties
• Spellcheck and suggestions: how checking behaves
• Privacy: what the component transmits, which is nothing