Migrating from #tiptap-editor

The former Nuxt module modules/tiptap-editor (alias #tiptap-editor, auto-imported components, composables and utils, one server directory) is gone. Nothing is auto-imported and no alias remains: import from the entries below.

1. nuxt.config.ts: replace './modules/tiptap-editor' with '@skaile/forge-editor/nuxt' (after '@nuxt/ui'). The tiptapEditor options keep their shape and defaults. Add "@skaile/forge-editor": "workspace:*" to the host's dependencies.
2. Replace auto-imported components and composables by explicit imports:

3. Collaboration, block UI and the integrations are now features. AdvancedEditor includes them; a custom preset adds collabFeature(), blockUiFeature() and the integrations explicitly. Features report user-facing messages through the surface's Notifier (ctx.notify, per-feature entries), so host code no longer hands toast objects to feature functions.
4. Search the host for #tiptap-editor, modules/tiptap-editor and for symbols that used to resolve without an import (useEditorSettings, useFileImport, ABILITY, fileNameError's neighbors…); nuxt typecheck reports every unresolved one.
5. Styles: the Nuxt module adds every feature stylesheet; a plain-Vue app imports core.css plus the feature CSS it uses (README).

Stored data needs no migration: document JSON, Yjs state, tiptap-editor:settings, tiptap-editor:model-profiles and tip-tree:node-filters keep their keys and shapes. Legacy section nodes are still migrated on load (currentContent on the server, the composites Feature's migrateContent hook in the editor).

Block vocabulary

The library, the reference app and the docs name things in the block vocabulary (glossary: Typed block, Block type, Property definition, Model role, …). The former names are removed; no alias remains. Switch a host over like this:

Behaviour that changed with the rename:

• Accepted children. The built-in Folder and Document Block types declare accepts: 'all' themselves; the id-keyed default is gone. A Block type without accepts, and a type ID that a list does not define, accepts no nested Typed blocks (acceptsChild). A host list that defines its own folder or document Block type must set accepts on it.
• Block UI. The hover bar, the toolbar Block actions and the drag handle address the outermost block, so a caret in a list item or a quote paragraph acts on the whole list or quote (Block UI).
• Labels. English: Typed block, Block type, Readable rendition, Theme with Default appearance, Document facts, Structure mode and Flat mode. German: Block and Blocktyp; the two German labels that still use the legacy words for basket and readable rendition stay. Message keys keep their IDs, so messages overrides still apply, but check the wording of an override against the new labels.

Block types as data

A BlockType (@skaile/forge-editor/composites) is now an id, its presentation (label, icon, titlePlaceholder, descriptionPlaceholder, chrome) and a list capabilities: { id, config? }[]. The former switches move into it (Typed blocks):

A host list that spreads defaultBlockTypes(t) and adds its own types must give them the capabilities they need. An unknown capability id or an invalid config throws when the editor is created. meta keys and the ::: <Block type id> Markdown fences keep their names; the node and its type attribute are renamed (below).

Persisted names

Stored documents and settings use the vocabulary of the glossary. Everything saved before loads through a migration that reads the old names and never writes them back; hosts do nothing for stored data.

Markdown needs no migration: the fence is ::: <Block type id> #id {meta} before and after, so old Markdown parses to Typed blocks and the export is byte-identical.

The server migrates Yjs state when a document loads (onLoadDocument, before any client syncs): it reads the schema-less JSON of the stored state, applies the same JSON migration and writes the result back with the block IDs and content unchanged, then persists the migrated state. A second load finds nothing to migrate. Client JSON goes through the rename in defineEditor, which runs ahead of any contributed migrateContent (the Typed blocks feature contributes the legacy-node migration), so a host hook cannot drop it.

Settings version 2 renamed four keys (table below). Saved settings (server store, localStorage) migrate on load and are rewritten once. The host config key change needs a code change (no migration).