Skip to content

chore(deps): update devdependencies (non-major) - #3089

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/dev-dependencies
Open

chore(deps): update devdependencies (non-major)#3089
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/dev-dependencies

Conversation

@renovate

@renovate renovate Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@tiptap/vue-3 (source) 3.29.23.30.1 age confidence
@types/semver (source) 7.7.17.8.0 age confidence
vue-tsc (source) 3.3.93.3.10 age confidence

Release Notes

ueberdosis/tiptap (@​tiptap/vue-3)

v3.30.1

Compare Source

Patch Changes

v3.30.0

Compare Source

Minor Changes
  • 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

    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

Patch Changes
vuejs/language-tools (vue-tsc)

v3.3.10

Compare Source

language-core
  • fix: ignore trailing whitespace after generic parameter commas - Thanks to @​KazariEX!
  • fix: resolve v-for item type over generic sources (#​6141) - Thanks to @​serkodev!
  • fix: do not extract SFC blocks across inline Markdown code (#​6145) - Thanks to @​lazerg!
language-service
  • fix: serialize template data provider access across concurrent requests (#​6154) - Thanks to @​serkodev!
tsc
  • fix: support different extension sets across project references (#​6146) - Thanks to @​lazerg!
typescript-plugin
vscode
  • feat: patch typescript.js via --require to support read-only file systems (#​6149) - Thanks to @​serkodev!
  • fix: isolate custom TypeScript plugin paths between profiles (#​6148) - Thanks to @​serkodev!

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/dev-dependencies branch 2 times, most recently from 496014d to 55fb8ac Compare August 14, 2026 11:58
@renovate
renovate Bot force-pushed the renovate/dev-dependencies branch from 55fb8ac to 4729a9d Compare August 15, 2026 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants