Packages

@tiptap/extension-table-of-contents

3.35.0 · 20 Nov 2026MIT490.1k / weekRepositoryHomepagenpmAtom feed

Your version

3.32.3

5 Nov 2026Where it was published

3.35.0 is the newest release of 3.x.

In short

1 new9 fixed

Release note

@tiptap/core

Patch Changes

  • Clearing formatting on a nested list now turns every level into paragraphs, and clearNodes() works in a chain with other node commands.

  • Stop removed resizable node views from responding to later editor updates.

@tiptap/extension-bubble-menu

Patch Changes

  • Bubble menus now update correctly after IME input, including Korean text

@tiptap/extension-code-block-lowlight

Patch Changes

  • Fixed a performance issue where code highlighting updates were unnecessarily triggered by selection-only changes

@tiptap/extension-floating-menu

Patch Changes

  • Floating menus now update correctly after IME input, including Korean text

@tiptap/extension-link

Patch Changes

  • Pasting a link without a protocol now uses the defaultProtocol option instead of always falling back to http.

@tiptap/extensions

Patch Changes

  • The Placeholder extension no longer leaves placeholders behind on empty nodes after the cursor moves away when includeChildren is enabled.

@tiptap/react

Patch Changes

  • Fix a React warning when a command like setContent creates React node views from inside an effect.

  • Fixed the cursor no longer following clicks after an editor inside a shadow root was unmounted and remounted.

@tiptap/vue-2

Patch Changes

  • Fixed the cursor no longer following clicks after an editor inside a shadow root was unmounted and remounted.

@tiptap/vue-3

Patch Changes

  • Fixed the cursor no longer following clicks after an editor inside a shadow root was unmounted and remounted.

@tiptap/y-tiptap

Minor Changes

  • Remove persistent position migrations to stop structural edits and undo or redo from adding migration history to collaborative documents. Saved relative positions no longer follow content that structural edits replace or move.

    Existing migration entries are deleted when an editor opens and when later Yjs updates arrive. Yjs can reclaim their stored data when garbage collection is enabled. Document content and other shared data are unchanged. Upgrade all collaborating clients to stop older clients from writing new entries.

    Documents that the server refuses to load need cleanup on the server before a client can repair them. With Yjs garbage collection disabled, deleting entries does not reclaim their stored data.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.