fix(deps): update tiptap monorepo to v3 (major)

Open renovate[bot] opened this issue 6 months ago • 1 comments

This PR contains the following updates:

Package	Change	Age	Confidence
@tiptap/core (source)	`2.26.1` -> `3.11.1`
@tiptap/extension-color (source)	`^2.11.5` -> `^3.0.0`
@tiptap/extension-gapcursor (source)	`^2.11.5` -> `^3.0.0`
@tiptap/extension-highlight (source)	`^2.11.5` -> `^3.0.0`
@tiptap/extension-table (source)	`^2.11.5` -> `^3.0.0`
@tiptap/extension-table-cell (source)	`^2.11.5` -> `^3.0.0`
@tiptap/extension-table-header (source)	`^2.11.5` -> `^3.0.0`
@tiptap/extension-table-row (source)	`^2.11.5` -> `^3.0.0`
@tiptap/extension-text-style (source)	`^2.11.5` -> `^3.0.0`
@tiptap/pm (source)	`2.26.1` -> `3.11.1`
@tiptap/starter-kit (source)	`2.26.1` -> `3.11.1`
@tiptap/vue-3 (source)	`2.26.1` -> `3.11.1`

Release Notes

ueberdosis/tiptap (@tiptap/core)

`v3.11.1`

Compare Source

Patch Changes

d0c4264: Improve TypeScript generics for Node.extend

The Node.extend method's TypeScript signature was updated so that ExtendedConfig can extend NodeConfig and MarkConfig, improving type inference when extending Node and Mark classes with additional config properties.

This is a type-only change — there are no runtime behavior changes.
- @tiptap/pm@3.11.1

`v3.11.0`

Compare Source

Minor Changes

541c93c: Add native text direction support for RTL and bidirectional content. The editor now includes a textDirection option that can be set to 'ltr', 'rtl', or 'auto' to control the direction of all content globally. Additionally, new setTextDirection and unsetTextDirection commands allow for granular control of text direction on specific nodes. This enables proper rendering of right-to-left languages like Arabic and Hebrew, as well as bidirectional text mixing multiple languages.

Patch Changes

@tiptap/pm@3.11.0

`v3.10.8`

Compare Source

Patch Changes

8375241: Fixed a bug that caused extra characters to be inserted after a parsed, nestable content block by accounting for leading newlines
b7ead7c: Add documentation comments to Tiptap JSON types
95d3e80: allow undefined as a value for the default attribute key
fd479bd: Fix updateAttributes and resetAttributes commands to return accurate results when used with .can(). Previously, these commands would always return true even when they couldn't perform the operation. Now they correctly return false when no matching nodes or marks are found in the selection.
- @tiptap/pm@3.10.8

`v3.10.5`

Compare Source

Patch Changes

92fae18: Fixed ProseMirror schema generation to properly respect isRequired attribute configuration. Previously, attributes marked with isRequired: true were incorrectly treated as optional because a default property was always included in the schema specification. ProseMirror determines attribute requirements by the absence of the default property, so now the default is only included when the attribute is not required and a default value is explicitly defined.
- @tiptap/pm@3.10.5

`v3.10.4`

Compare Source

Patch Changes

64561c4: Fix autofocus behavior to prevent unwanted scrolling when disabled
- @tiptap/pm@3.10.4

`v3.10.1`

Compare Source

Patch Changes

3564e7c: Use correct ResizableNodeView class name
- @tiptap/pm@3.10.1

`v3.10.0`

Compare Source

Minor Changes

4aa9f57: Add a new ResizableNodeview NodeView to core that wraps elements (images, videos, iframes) with configurable resize handles. It provides live onResize/onCommit callbacks, min/max constraints, aspect-ratio support, and styling hooks (class names + data attributes) to improve UX when resizing media inside the editor.
4aa9f57: the addNodeView function can now return null to dynamically disable rendering of a node view

While this should not directly cause any issues, it's noteworthy as it still could affect some behavior in some edge cases.

Patch Changes

@tiptap/pm@3.10.0

`v3.9.0`

Compare Source

Patch Changes

bbb8e16: Only remove injected CSS on unmount if no other editors are in the document (fixes #6836)
- @tiptap/pm@3.9.0

`v3.8.0`

Compare Source

Releases

v3.8.0

@tiptap/extension-unique-id @3.8.0

Minor Changes

23e516e: Add updateDocument option to disable document updates caused by the Unique ID extension.

Patch Changes

f3770af: Prevent Bubble Menu plugin from re-loading every time the BubbleMenu component re-renders. Reverts a regression introduced in v3.6.3, in PR #7028.

`v3.7.2`

Compare Source

Releases

v3.7.2

Patch Changes

Fix CVE-2025-62410 by updating happy-dom to ^20.0.2

`v3.7.1`

Compare Source

Releases

v3.7.1

Patch Changes

Editors will not throw an error anymore when content is an empty string and contentType is markdown
Remove invalid server configuration from package.json

Releases

v3.7.0

Minor Changes

All commands and their corresponding TypeScript types are now exported from @tiptap/core so they can be imported and referenced directly by consumers. This makes it easier to build typed helpers, extensions, and tests that depend on the command signatures.

Why:
- Previously some command option types were only available as internal types or scattered across files, which made it awkward for downstream users to import and reuse them.
```
import { commands } from '@&#8203;tiptap/core'
```
Notes:
- This is a non-breaking, additive change. It improves ergonomics for TypeScript consumers.
- If you rely on previously private/internal types, prefer the exported types from @tiptap/core going forward.
Add comprehensive bidirectional markdown support to Tiptap through a new @tiptap/markdown package and Markdown utilities in @tiptap/core.

New Package: @tiptap/markdown - A new official extension that provides full Markdown parsing and serialization capabilities using MarkedJS as the underlying Markdown parser.

Core Features:

Extension API
- Markdown Extension: Main extension that adds Markdown support to your editor
- MarkdownManager: Core engine for parsing and serializing Markdown
  - Parse Markdown strings to Tiptap JSON: editor.markdown.parse(markdown)
  - Serialize Tiptap JSON to Markdown: editor.markdown.serialize(json)
  - Access to underlying marked.js instance: editor.markdown.instance

Editor Methods

editor.getMarkdown(): Serialize current editor content to Markdown string
editor.markdown: Access to MarkdownManager instance for advanced operations

Editor Options:

contentType: Control the type of content that is inserted into the editor. Can be json, html or markdown - defaults to json and will automatically detect invalid content types (like JSON when it is actually Markdown).
```
new Editor({
  content: '# Hello World',
  contentType: 'markdown'
})
```

Command Options: All content commands now support an contentType option:

setContent(markdown, { contentType: 'markdown' }): Replace editor content with markdown
insertContent(markdown, { contentType: 'markdown' }): Insert markdown at cursor position
insertContentAt(position, markdown, { contentType: 'markdown' }): Insert Markdown at specific position

For more, check the documentation.

Patch Changes

The extension manager now provides a new property baseExtensions that contains an unflattened array of extensions

Minor Changes

Add comprehensive bidirectional markdown support to Tiptap through a new @tiptap/markdown package and Markdown utilities in @tiptap/core.

New Package: @tiptap/markdown - A new official extension that provides full Markdown parsing and serialization capabilities using MarkedJS as the underlying Markdown parser.

Core Features:

Extension API
- Markdown Extension: Main extension that adds Markdown support to your editor
- MarkdownManager: Core engine for parsing and serializing Markdown
  - Parse Markdown strings to Tiptap JSON: editor.markdown.parse(markdown)
  - Serialize Tiptap JSON to Markdown: editor.markdown.serialize(json)
  - Access to underlying marked.js instance: editor.markdown.instance

Editor Methods

editor.getMarkdown(): Serialize current editor content to Markdown string
editor.markdown: Access to MarkdownManager instance for advanced operations

Editor Options:

contentType: Control the type of content that is inserted into the editor. Can be json, html or markdown - defaults to json and will automatically detect invalid content types (like JSON when it is actually Markdown).
```
new Editor({
  content: '# Hello World',
  contentType: 'markdown'
})
```

Command Options: All content commands now support an contentType option:

setContent(markdown, { contentType: 'markdown' }): Replace editor content with markdown
insertContent(markdown, { contentType: 'markdown' }): Insert markdown at cursor position
insertContentAt(position, markdown, { contentType: 'markdown' }): Insert Markdown at specific position

For more, check the documentation.

Patch Changes

Paste Handlers and onPaste plugin now respect shouldAutoLink/validate options

Patch Changes

Make the TrailingNode extension's node option optional and derive the default node type from the editor schema when available.

Previously the extension used a hard-coded 'paragraph' default and the node option was required in the TypeScript definitions. This change:
- makes node optional in the options type,
- prefers the editor schema's top node default type when resolving the trailing node, and
- falls back to the configured option or 'paragraph' as a last resort.
This fixes cases where projects use a different top-level default node and prevents the extension from inserting an incorrect trailing node type.

`v3.6.5`

Compare Source

Patch Changes

1e4caea: Editors can now emit transaction and update events before being mounted. This means smoother state handling and instant feedback from editors, even when they're not in the DOM.
- @tiptap/pm@3.6.5

`v3.6.3`

Compare Source

Patch Changes

67f7b4a: Refined the JSONContent.attrs definition to exactly mirror the structure returned by editor.getJSON(). This ensures strict type safety and consistency between the editor output and the expected type, eliminating errors caused by mismatched attribute signatures.
- @tiptap/pm@3.6.3

`v3.6.0`

Compare Source

Patch Changes

c0190bd: Improve typing and docs for EditorOptions.element to reflect all supported mounting modes and align behavior across adapters.
- element now accepts:
  - Element: the editor is appended inside the given element.
  - { mount: HTMLElement }: the editor is mounted directly to mount (no extra wrapper).
  - (editorEl: HTMLElement) => void: a function that receives the editor element so you can place it anywhere in the DOM.
  - null: no automatic mounting.
- @tiptap/pm@3.6.0

`v3.4.6`

Compare Source

Patch Changes

968016f: Added support for the undoable option in InputRules (matching ProseMirror’s implementation).
- When false, the change will not be tracked as undoable.
- Default remains true for backward compatibility.
This brings Tiptap’s InputRules behavior in line with ProseMirror and gives developers finer control over undo functionality.
- @tiptap/pm@3.4.6

`v3.4.5`

Compare Source

Patch Changes

0226d42: Fix an issue where injected CSS was not mounted correctly when the editor instance was mounted. The fix ensures CSS injected by the editor is attached to the document when the editor mounts, preventing missing styles in some mount/unmount scenarios.
37af83b: refactor: replace map(...).flat() with flatMap for simpler, more efficient array flattening
f598ac7: Fix bug in insertContentAt command where extra content would get deleted when the selection was at the beginning of the document and a node was inserted
- @tiptap/pm@3.4.5

`v3.4.4`

Compare Source

Patch Changes

00cf1d7: Fix bug in insertContentAt command where extra content would get deleted when the selection was at the beginning of the document and a node was inserted
- @tiptap/pm@3.4.4

`v3.4.3`

Compare Source

Patch Changes

1ea8906: When the editor view is created, it now will also include nodeViews and markViews properties instead of setting them afterward. This avoids serialization of the editor state to HTML which will be replaced by node views anyway.
- @tiptap/pm@3.4.3

`v3.4.0`

Compare Source

Minor Changes

ad51daa: Add mount and unmount events to the Editor instance for tracking mounts and unmounts

Patch Changes

895c73f: Fix can().toggleMark() returning incorrect result when cursor is inside nodes that disallow marks

Fixed an issue where can().toggleMark('bold') incorrectly returned true when the cursor was positioned inside a code block (with no selection), even though marks are not allowed in code blocks. The method now correctly returns false in this scenario by checking if the parent node allows the mark type when the selection is a cursor.
- @tiptap/pm@3.4.0

`v3.3.0`

Compare Source

Minor Changes

5423726: Make input rules and paste rules respect extension priority by registering them per-extension instead of aggregating them into a single global plugin.

`v3.2.1`

Patch Changes

6a2873f: Ensure drag previews for node views work correctly in Safari by attaching an offscreen clone of the node to the DOM while calling setDragImage, and by preserving the original element's pixel width/height so the preview matches the original. This prevents Safari from immediately cancelling the drag when a detached element is used as the drag image.
- @tiptap/pm@3.2.1

`v3.2.0`

Minor Changes

5056e3e: Fix Editor.unmount() failing in test environments due to missing DOM remove() method

Patch Changes

@tiptap/pm@3.2.0

`v3.0.6`

Compare Source

Patch Changes

2e71d05: Fix: Fix broken types for function chaining when calling extend
- @tiptap/pm@3.0.6

`v3.0.4`

Compare Source

Patch Changes

7ed03fa: Fix: Add correct overload for extension extend types"
- @tiptap/pm@3.0.4

`v3.0.3`

Compare Source

Patch Changes

75cabde: Fix: Avoid the JSX Runtime to globally overwrite React's Element types when /** @jsxImportSource @tiptap/core */ is not used
- @tiptap/pm@3.0.3

`v3.0.1`

Compare Source

Major Changes

a92f4a6: We are now building packages with tsup which does not support UMD builds, please repackage if you require UMD builds
5e957e5: This resolves in issue with SSR where the isDestroyed property could not be read while in SSR

37913d5: getPos in NodeViewRendererProps type now includes undefined as possible return value

Before

const pos = nodeViewProps.getPos() // Type was () => number

After

const pos = nodeViewProps.getPos() // Type is () => number | undefined

if (pos !== undefined) {
  // Safe to use pos here
}

32958d6: Node, Mark and Extension config options now are strongly typed and do not allow arbitrary keys on the options object.

To add keys, like when using extendNodeSchema or extendMarkSchema, you can do this:

declare module '@&#8203;tiptap/core' {
  interface NodeConfig {
    /**
     * This key will be added to all NodeConfig objects in your project
     */
    newKey?: string
  }
  interface MarkConfig {
    /**
     * This key will be added to all MarkConfig objects in your project
     */
    newKey?: string
  }
  interface ExtensionConfig {
    /**
     * This key will be added to all ExtensionConfig objects in your project
     */
    newKey?: string
  }
}

12bb31a: insertContent and insertContentAt commands should not split text nodes like paragraphs into multiple nodes when the inserted content is at the beginning of the text to avoid empty nodes being created
062afaf: clearContent command defaults to emitting updates now
062afaf: Change signature of setContent command to (content, options) and default to emitting updates
32958d6: editor.storage is now strongly typed Storage instances, using a similar pattern as commands, where you can define the type of the storage value using namespaces like:
```
declare module '@&#8203;tiptap/core' {
  interface Storage {
    extensionName: StorageValue
  }
}
```
32958d6: editor.storage is instantiated per editor rather than per extension.

Previously, the storage value was a singleton per extension instance, this caused strange bugs when using multiple editor instances on a single page.

Now, storage instances are per editor instance, so changing the value on one editor.storage instance will not affect another editor's value.

Minor Changes

8de8e13: The editor instance now supports an unmount method which allows for mounting and unmounting the editor to the DOM. This encourages re-use of editor instances by preserving all the same options between instances. This is different from the destroy method, which will unmount, emit the destroy event, and remove all event listeners.
d0fda30: Add config option to emit content error when content check is disabled

0e3207f: Add support for markviews, which allow you to render custom views for marks within the editor. This is useful for rendering custom UI for marks, like a color picker for a text color mark or a link editor for a link mark.

Here is a plain JS markview example:

Mark.create({
  // Other options...
  addMarkView() {
    return ({ mark, HTMLAttributes }) => {
      const dom = document.createElement('b')
      const contentDOM = document.createElement('span')

      dom.appendChild(contentDOM)

      return {
        dom,
        contentDOM,
      }
    }
  },
})

`v3.0.0`

Compare Source

Patch Changes

@tiptap/pm@3.0.0-beta.30

ueberdosis/tiptap (@tiptap/extension-color)

`v3.11.1`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.11.1

`v3.11.0`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.11.0

`v3.10.8`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.10.8

`v3.10.7`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.10.7

`v3.10.6`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.10.6

`v3.10.5`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.10.5

`v3.10.4`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.10.4

`v3.10.3`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.10.3

`v3.10.2`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.10.2

`v3.10.1`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.10.1

`v3.10.0`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.10.0

`v3.9.1`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.9.1

`v3.9.0`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.9.0

`v3.8.0`

Compare Source

Patch Changes

@tiptap/extension-text-style@3.8.0

`v3.7.2`

Compare Source

Releases

v3.7.2

@tiptap/html

Patch Changes

Fix CVE-2025-62410 by updating happy-dom to ^20.0.2

`v3.7.1`

Compare Source

Releases

v3.7.1

@tiptap/markdown

Patch Changes

Editors will not throw an error anymore when content is an empty string and contentType is markdown
Remove invalid server configuration from package.json

`v3.7.0`

Compare Source

Releases

v3.7.0

@tiptap/core

Minor Changes

All commands and their corresponding TypeScript types are now exported from @tiptap/core so they can be imported and referenced directly by consumers. This makes it easier to build typed helpers, extensions, and tests that depend on the command signatures.

Why:
- Previously some command option types were only available as internal types or scattered across files, which made it awkward for downstream users to import and reuse them.
```
import { commands } from '@&#8203;tiptap/core'
```
Notes:
- This is a non-breaking, additive change. It improves ergonomics for TypeScript consumers.
- If you rely on previously private/internal types, prefer the exported types from @tiptap/core going forward.
Add comprehensive bidirectional markdown support to Tiptap through a new @tiptap/markdown package and Markdown utilities in @tiptap/core.

New Package: @tiptap/markdown - A new official extension that provides full Markdown parsing and serialization capabilities using MarkedJS as the underlying Markdown parser.

Core Features:

Extension API
- Markdown Extension: Main extension that adds Markdown support to your editor
- MarkdownManager: Core engine for parsing and serializing Markdown
  - Parse Markdown strings to Tiptap JSON: editor.markdown.parse(markdown)
  - Serialize Tiptap JSON to Markdown: editor.markdown.serialize(json)
  - Access to underlying marked.js instance: editor.markdown.instance

Editor Methods

editor.getMarkdown(): Serialize current editor content to Markdown string
editor.markdown: Access to MarkdownManager instance for advanced operations

Editor Options:

contentType: Control the type of content that is inserted into the editor. Can be json, html or markdown - defaults to json and will automatically detect invalid content types (like JSON when it is actually Markdown).
```
new Editor({
  content: '# Hello World',
  contentType: 'markdown'
})
```

Command Options: All content commands now support an contentType option:

setContent(markdown, { contentType: 'markdown' }): Replace editor content with markdown
insertContent(markdown, { contentType: 'markdown' }): Insert markdown at cursor position
insertContentAt(position, markdown, { contentType: 'markdown' }): Insert Markdown at specific position

For more, check the documentation.

Patch Changes

The extension manager now provides a new property baseExtensions that contains an unflattened array of extensions

@tiptap/markdown

Minor Changes

Add comprehensive bidirectional markdown support to Tiptap through a new @tiptap/markdown package and Markdown utilities in @tiptap/core.

New Package: @tiptap/markdown - A new official extension that provides full Markdown parsing and serialization capabilities using MarkedJS as the underlying Markdown parser.

Core Features:

Extension API
- Markdown Extension: Main extension that adds Markdown support to your editor
- MarkdownManager: Core engine for parsing and serializing Markdown
  - Parse Markdown strings to Tiptap JSON: editor.markdown.parse(markdown)
  - Serialize Tiptap JSON to Markdown: editor.markdown.serialize(json)
  - Access to underlying marked.js instance: editor.markdown.instance

Editor Methods

editor.getMarkdown(): Serialize current editor content to Markdown string
editor.markdown: Access to MarkdownManager instance for advanced operations

Editor Options:

contentType: Control the type of content that is inserted into the editor. Can be json, html or markdown - defaults to json and will automatically detect invalid content types (like JSON when it is actually Markdown).
```
new Editor({
  content: '# Hello World',
  contentType: 'markdown'
})
```

Command Options: All content commands now support an contentType option:

setContent(markdown, { contentType: 'markdown' }): Replace editor content with markdown
insertContent(markdown, { contentType: 'markdown' }): Insert markdown at cursor position
insertContentAt(position, markdown, { contentType: 'markdown' }): Insert Markdown at specific position

For more, check the documentation.

@tiptap/extension-link

Patch Changes

Paste Handlers and onPaste plugin now respect shouldAutoLink/validate options

@tiptap/extensions

Patch Changes

Make the TrailingNode extension's node option optional and derive the default node type from the editor schema when available.

Previously the extension used a hard-coded 'paragraph' default and the node option was required in the TypeScript definitions. This change:
- makes node optional in the options type,
- prefers the editor schema's top node default type when resolving the trailing node, and
- falls back to the configured option or 'paragraph' as a last resort.
This fixes cases where projects use a different top-level default node and prevents the extension from inserting an incorrect trailing node type.