chore(deps): update tiptap to ^3.31.3, pin prosemirror-view (nuxt/ui@042bf3b)

[IgorShevchik]

Port of nuxt/ui@042bf3b7 — fourth of ten in this run.

The bump

All 25 @tiptap/* declarations across five manifests sat at ^3.30.5, upstream's exact pre-image — playgrounds/demo included. Demo is ours alone and carries @tiptap/extension-emoji and @tiptap/extension-text-align like its siblings; holding it a minor behind would serve nothing, the same reasoning recorded for 9d46fc7e.

Three names upstream lists are absent here: @tiptap/core, @tiptap/pm and @tiptap/vue-3 under playgrounds/nuxt, which that playground does not declare directly.

The @tiptap/pm override in pnpm-workspace.yaml moves with the family, as its own comment instructs. Verified: one @tiptap/pm@3.31.3 in the lockfile.

The companion change, which the existing override's comment predicted

The bump broke typecheck in all three copies of the editor completion extension:

EditorCompletionExtension.ts(85,11): error TS2322: Type
'(this: Plugin<any>, state: EditorState) => DecorationSet' is not assignable to
'(this: Plugin<any>, state: EditorState) => DecorationSource | null | undefined'

That reads like an API change and is not one. It is two copies of prosemirror-view, so DecorationSet comes from one and DecorationSource from the other — unrelated types with the same names.

Measured against main rather than inferred:

	prosemirror-view	@tiptap/pm
main	1.42.0	3.30.5
after the bump	1.42.0 and 1.42.3	3.31.3

Traced: @tiptap/pm@3.31.3 wants 1.42.3, while prosemirror-dropcursor, -gapcursor, -history, -state and -tables peer-accept a range and had settled on 1.42.0.

This is exactly the failure the @tiptap/pm override exists to prevent, arriving one level down — and that override could not prevent it, because pinning the tiptap wrapper keeps one wrapper, not one prosemirror-view. So the override gains a sibling, prosemirror-view: ^1.42.3, with the reasoning beside it. After that: a single 1.42.3, and typecheck is clean.

@tiptap/core resolves to two versions — and that is not this commit's doing

main already had 3.30.2 and 3.30.5; the pair is now 3.30.5 and 3.31.3. The older line lives entirely under @nuxt/ui@4.8.2, which reaches this tree through nuxtseo-layer-devtools — a devtools dependency that never touches our Editor. Checked rather than assumed: no importer references the old version, and the package pulling it is named in the lockfile.

Recorded because a reader comparing @tiptap/core counts before and after would otherwise suspect this change.

Bookkeeping

• .sync/nuxt-ui.json — cursor 2d4782ba → 042bf3b7, entry added; 2d4782ba reconciled to fix(InputNumber): work uncontrolled with only a default value (nuxt/ui@2d4782b) #552 / 704312db.
• .sync/dep-parity.json — refreshed at the new cursor.
• .sync/log/042bf3b7….md — the long-form reasoning.

Resolved versions read from pnpm-lock.yaml, not node_modules. Local gate green: lint · typecheck · build (3.87 MB) · test (347 files, 7895 passed, 6 skipped) · test:module · repl:build.

Still ahead

Six upstream commits: 7224333b (upstream's own release), 5fd94e13 (theme editor docs), 9076ca2d (virtualizer size fallback), and three docs-only commits.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JS8ypVfQSFzYVZzkTHhURb

---

Generated by Claude Code