deps(deps): bump @tiptap/core from 2.27.2 to 3.30.1

[dependabot]

Bumps @tiptap/core from 2.27.2 to 3.30.1.

Release notes

Sourced from @​tiptap/core's releases.

v3.30.1

@​tiptap/extension-table

Patch Changes

• Fixed table markdown pipe escaping so the extension loads on older Safari and iOS versions (WebKit before Safari 16.4).

@​tiptap/core

Patch Changes

• Added new ProseMirror helpers that check whether a value is a specific ProseMirror type.

v3.30.0

@​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.

... (truncated)

Changelog

Sourced from @​tiptap/core's changelog.

3.30.1

Patch Changes

• abc8828: Added new ProseMirror helpers that check whether a value is a specific ProseMirror type.
  • @​tiptap/pm@​3.30.1

3.30.0

Minor Changes

• 0247d39: 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.

• 3099eef: 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

... (truncated)

Commits

• 4c4933d chore(release): release new stable release (#8181)
• abc8828 feat(core): add ProseMirror type guard functions (#8186)
• 7901bc2 chore(release): release new stable release (#8142)
• 3099eef feat(core): add Decorations API with framework widget renderers (#7902)
• 51909d3 fix(core): insert content when prosemirror-model is loaded more than once (#8...
• 0247d39 feat(extension-list-keymap): sink paragraph into previous list item on tab (#...
• 5158212 chore(release): release new stable release (#8132)
• 896564a chore(release): release new stable release (#8128)
• 1afef87 chore(release): release new stable release (#8087)
• 51f45b6 fix(core): seed editor state from fallback doc so onContentError is usable (#...
• Additional commits viewable in compare view

[dependabot]

Superseded by #52.