@tiptap/extension-find-and-replace

@tiptap/markdown

Patch Changes

• A literal ! directly before a link is now escaped when serializing to Markdown, so the link is no longer parsed back as an image.

@tiptap/pm

Patch Changes

• Update ProseMirror dependencies to their latest versions.

@tiptap/react

Patch Changes

• Fix useEditorState overflowing the stack when a selector returns a value with circular references, such as editor.state after one stored mark replaces another.

@tiptap/core

Minor Changes

• Add the schemaSpec editor option to use an external ProseMirror schema structure with local extension behavior.

Patch Changes

• Fix list toggling between list types that use different item nodes. Nested lists are recursively converted when the target item schema supports nesting, and flattened into sibling items when it does not.

@tiptap/y-tiptap

Patch Changes

• Keep relative text and node positions attached through structural edits, node moves, and undo or redo across collaborating clients.

• Improve TypeScript definitions for document synchronization, shared cursors, undo, redo, and document conversions.

• Improve collaboration performance and keep comments, highlights, caret positions, and remote caret details intact during remote edits.

• Preserve shared content when a client cannot display its nodes or marks, and pause that client's editing until compatible content is available.

  Headless document creation rejects empty content when the schema requires child nodes.

@tiptap/extension-collaboration

Patch Changes

• Keep collaborative editing, cursor presence, and drag handles compatible with the updated @tiptap/y-tiptap binding.

@tiptap/extension-collaboration-caret

Patch Changes

• Keep collaborative editing, cursor presence, and drag handles compatible with the updated @tiptap/y-tiptap binding.

@tiptap/extension-drag-handle

Patch Changes

• Keep collaborative editing, cursor presence, and drag handles compatible with the updated @tiptap/y-tiptap binding.

@tiptap/ai-toolkit

Patch Changes

• Keep collaborative editing, cursor presence, and drag handles compatible with the updated @tiptap/y-tiptap binding.

@tiptap/extension-mathematics

Patch Changes

• The mathematics extension no longer crashes the editor in older WebKit browsers and WKWebView.

@tiptap/core

Patch Changes

• Fix a TypeError thrown when the source editor is destroyed right after dragging content into another editor.

• splitBlock no longer throws TransformError: Inserted content deeper than insertion position when the selection spans block boundaries (for example from the start of one paragraph into another block, or across an isolating node). The command now returns false when the split is not possible.

• Prevent extra CSS declarations from being rendered from editor content.

• Atom block directives (:::name {…} :::) indented by up to 3 spaces are now tokenized, matching CommonMark indentation rules for block constructs.

• Numeric HTML entities (', ') are now decoded when parsing markdown, instead of showing up as literal text in the editor.

• The editor element keeps role="textbox" after setOptions() when editorProps.attributes is set. Before, a re-render in React replaced the default role with the user attributes. Attributes passed as a function now get the default role as well.

• Undoing an input rule restores the Markdown characters that triggered it when using Collaboration.

• Bind parseMarkdown and renderMarkdown to the configured extension so hooks can read this.options and this.name without an Editor.

• Pressing Enter before the text of a checked task item now leaves the new empty item unchecked and the item with the text checked. Attributes declared with keepOnSplit: false now reset on the new item, not on the one that keeps the text.

• Stop joinItemForward and joinItemBackward from joining across isolating nodes.

• Node views without a contentDOM no longer ignore selection mutations, so ProseMirror moves the caret back to a valid position when the browser places it inside the node view.

@tiptap/markdown

Patch Changes

• Fix Markdown serialization of inline code containing backticks

• Bind parseMarkdown and renderMarkdown to the configured extension so hooks can read this.options and this.name without an Editor.

@tiptap/extension-code

Patch Changes

• Fix Markdown serialization of inline code containing backticks

@tiptap/extension-table

Patch Changes

• Table cells exported to Markdown now escape literal pipe characters, so the cell content survives when the output is read back.

• Multi-block table cells no longer leak a U+001F control character into Markdown.

• Right-clicking a cell inside a multi-cell table selection no longer collapses that selection.

• Prevent extra CSS declarations from being rendered from editor content.

• Table cells and headers no longer render the default colspan="1" and rowspan="1" attributes. Cells that actually span still render them, matching how prosemirror-tables serializes spans.

@tiptap/extension-list

Patch Changes

• Parsing large Markdown documents that contain ordered lists is much faster. A 578KB document went from about 19s to about 160ms.

@tiptap/extension-collaboration-caret

Patch Changes

• Prevent extra CSS declarations from being rendered from editor content.

@tiptap/extension-highlight

Patch Changes

• Prevent extra CSS declarations from being rendered from editor content.

@tiptap/extension-text-align

Patch Changes

• Prevent extra CSS declarations from being rendered from editor content.

@tiptap/extension-text-style

Patch Changes

• Prevent extra CSS declarations from being rendered from editor content.

@tiptap/extension-link

Patch Changes

• Typing spaces after a link no longer extends the link, including multiple spaces inserted in one transaction. Formatting changes and undo/redo preserve existing linked whitespace.

@tiptap/react

Patch Changes

• Fix Enter and Shift-Enter inside React node views on iOS and Android.

• React and Vue now use matching menu extension versions when installed from a specific release.

@tiptap/static-renderer

Patch Changes

• Render <audio> and <video> with a closing tag instead of self-closing them, so browsers no longer nest the following content inside the first audio element.

• Rendering a node whose renderHTML returns several nested child elements no longer adds stray commas between them in the HTML string output.

@tiptap/extension-collaboration

Patch Changes

• Undoing an input rule restores the Markdown characters that triggered it when using Collaboration.

@tiptap/vue-2

Patch Changes

• React and Vue now use matching menu extension versions when installed from a specific release.

@tiptap/vue-3

Patch Changes

• React and Vue now use matching menu extension versions when installed from a specific release.

@tiptap/core

Patch Changes

• Nested lists exported to Markdown now keep their hierarchy when the file is read back by other Markdown tools.

@tiptap/extension-list

Patch Changes

• Nested lists exported to Markdown now keep their hierarchy when the file is read back by other Markdown tools.

@tiptap/extension-youtube

Patch Changes

• Pasting a YouTube iframe without a src attribute no longer crashes the editor. The embed is kept without a source.

@tiptap/markdown

Patch Changes

• Fix Markdown serialization of whitespace-only marked text.

@tiptap/react

Patch Changes

• Reduce overhead in React node views on documents with many nodes.

@tiptap/extension-text-style

Patch Changes

• Unsetting one text style inside a blockquote no longer removes the other text styles in it.

@tiptap/extension-youtube

Patch Changes

• YouTube live URLs (/live/<id>) now embed the video.

@tiptap/core

Patch Changes

• Fix JSX runtime to properly render nested sibling elements by spreading children arrays into DOMOutputSpec

@tiptap/react

Patch Changes

• Fix ReactNodeViewRenderer crash when contentComponent is not available

@tiptap/ai-toolkit

Minor Changes

• Add the AiInsertReveal extension (@tiptap/ai-toolkit/streaming-reveal) to fade in text as the AI streams it into a collaborative document.

@tiptap/vue-2

Minor Changes

• ceb0dac: New Decorations API

  Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

  Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

  Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

  addDecorations() {
    return {
      create: ({ state }) =>
        // findMatches can be any function that returns an array of { from, to } ranges
        findMatches(state.doc).map(match =>
          Decoration.Inline(match.from, match.to, { class: 'highlight' }),
        ),
    }
  }

  There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

  Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

  Doing less work on every keystroke

  By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

  shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

  update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

  For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

  React and Vue components as widgets

  ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

  Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

  Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

  Documentation

  • Decorations

  • Decorations with React

  • Decorations with Vue

  • API Documentation

Patch Changes

• ceb0dac: Fix FloatingMenu not registering when the editor prop is provided synchronously, which prevented the menu from appearing

@tiptap/extension-list

Minor Changes

• ceb0dac: ListKeymap now registers a Tab shortcut that sinks a top-level textblock into the previous list's last item. Pressing Tab at the start of a paragraph right after a bullet/ordered/task list moves the paragraph inside the last list item. The handler does nothing when the cursor is already inside a list item (sinkListItem keeps working), when there is no list before the paragraph, when the caret is mid-textblock, or when the selection is not a text selection (for example a gap cursor).

  @tiptap/core also exposes a new getPreviousBlockSibling($pos) helper that returns the block-level sibling before the cursor's textblock, or null at the first child of the block parent.

Patch Changes

• ceb0dac: Parse block math that follows an ordered list item without a blank line, both after the list and indented inside the item, instead of pulling it into the item's text.

• ceb0dac: TaskItem: the checkbox label now also fills the wrapping label element, so accessibility audits no longer flag it as empty.

@tiptap/core

Minor Changes

• ceb0dac: ListKeymap now registers a Tab shortcut that sinks a top-level textblock into the previous list's last item. Pressing Tab at the start of a paragraph right after a bullet/ordered/task list moves the paragraph inside the last list item. The handler does nothing when the cursor is already inside a list item (sinkListItem keeps working), when there is no list before the paragraph, when the caret is mid-textblock, or when the selection is not a text selection (for example a gap cursor).

  @tiptap/core also exposes a new getPreviousBlockSibling($pos) helper that returns the block-level sibling before the cursor's textblock, or null at the first child of the block parent.

• ceb0dac: New Decorations API

  Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

  Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

  Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

  addDecorations() {
    return {
      create: ({ state }) =>
        // findMatches can be any function that returns an array of { from, to } ranges
        findMatches(state.doc).map(match =>
          Decoration.Inline(match.from, match.to, { class: 'highlight' }),
        ),
    }
  }

  There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

  Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

  Doing less work on every keystroke

  By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

  shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

  update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

  For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

  React and Vue components as widgets

  ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

  Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

  Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

  Documentation

  • Decorations

  • Decorations with React

  • Decorations with Vue

  • API Documentation

Patch Changes

• ceb0dac: Fixed insertContent, insertContentAt and setContent failing when prosemirror-model is loaded more than once.

@tiptap/starter-kit

Patch Changes

• ceb0dac: StarterKit now pins its bundled @tiptap/* dependencies to the exact version it was released with, so installing a specific StarterKit version gives you that version's extension set instead of the newest one.

@tiptap/react

Minor Changes

• ceb0dac: New Decorations API

  Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

  Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

  Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

  addDecorations() {
    return {
      create: ({ state }) =>
        // findMatches can be any function that returns an array of { from, to } ranges
        findMatches(state.doc).map(match =>
          Decoration.Inline(match.from, match.to, { class: 'highlight' }),
        ),
    }
  }

  There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

  Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

  Doing less work on every keystroke

  By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

  shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

  update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

  For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

  React and Vue components as widgets

  ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

  Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

  Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

  Documentation

  • Decorations

  • Decorations with React

  • Decorations with Vue

  • API Documentation

Patch Changes

• ceb0dac: React node views no longer show the selected state when the selection covers a position the node view has moved away from.

@tiptap/markdown

Patch Changes

• ceb0dac: Markdown with inline HTML such as an unclosed <b> tag no longer parses into an invalid document. The tag is dropped and its text is kept.

@tiptap/static-renderer

Patch Changes

• ceb0dac: Fixed table cell and header spans in the React static renderer.

@tiptap/pm

Patch Changes

• ceb0dac: Fix the ./schema-list export map pointing types at dist/schema/, which is not emitted. Tools that read the types condition directly could not resolve @tiptap/pm/schema-list.

@tiptap/extension-table

Patch Changes

• ceb0dac: Deleting the last row or column of a table no longer moves the cursor outside the table when there is content below it.

@tiptap/extension-drag-handle-react

Patch Changes

• ceb0dac: Fixed the React DragHandle breaking drag-and-drop when onNodeChange is an inline callback, by no longer re-registering its plugin when a callback's identity changes.

@tiptap/extension-mathematics

Patch Changes

• ceb0dac: Allow KaTeX 0.18 to be installed with the math extension

@tiptap/extension-blockquote

Patch Changes

• ceb0dac: Fixed Backspace freezing after merging a paragraph into a blockquote.

@tiptap/vue-3

Minor Changes

• ceb0dac: New Decorations API

  Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

  Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

  Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

  addDecorations() {
    return {
      create: ({ state }) =>
        // findMatches can be any function that returns an array of { from, to } ranges
        findMatches(state.doc).map(match =>
          Decoration.Inline(match.from, match.to, { class: 'highlight' }),
        ),
    }
  }

  There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

  Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

  Doing less work on every keystroke

  By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

  shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

  update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

  For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

  React and Vue components as widgets

  ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

  Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

  Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

  Documentation

  • Decorations

  • Decorations with React

  • Decorations with Vue

  • API Documentation