@platejs/yjs: allow @hocuspocus/provider v4 in peerDependencies #5337

Bug type

Behavior bug (incorrect output/state without crash)

Browser surface

No

Owner surface

Plate framework or plugin

Summary

@platejs/yjs@53.2.0 declares the peer dependency "@hocuspocus/provider": "^3.4.0", so installing it next to the current @hocuspocus/provider 4.x produces an unmet peer dependency.

Public reproduction URL

NOT_ENOUGH_INFO

Steps to reproduce

1. In any pnpm project run pnpm add @platejs/yjs@53.2.0 @hocuspocus/provider@4.8.0.
2. Observe the unmet peer warning for @hocuspocus/provider.

Expected behavior

The peer range accepts provider v4 (current stable is 4.8.0), for example ^3.4.0 || ^4.0.0, or the docs state that v4 is unsupported.

Actual behavior

pnpm reports an unmet peer: @hocuspocus/provider expected ^3.4.0, found 4.8.0. At runtime we see no problems: we run YjsPlugin with the Hocuspocus provider 4.x in production since 19.09.2026 (sync, awareness, cursors, HocuspocusProviderWrapper.provider).

Acceptance criteria

• No unmet peer warning with @hocuspocus/provider 4.x.
• Ideally a CI check of @platejs/yjs against provider v4.

Regression range

last-known-good: NOT_ENOUGH_INFO
first-known-bad: NOT_ENOUGH_INFO
evidence: peerDependencies of @platejs/yjs 53.2.0 and of main

Reproducibility

Always

Plate / Plite / React versions

platejs 53.3.11, @platejs/yjs 53.2.0, yjs 13.6.33, React 19

Operating system

macOS and Linux

Install method

pnpm 10.34.5

Framework / app setup

Next.js 16 app, Node 24

Affected packages or entry points

@platejs/yjs (package.json peerDependencies)

Minimal code or config excerpt

"peerDependencies": { "@hocuspocus/provider": "^3.4.0" }

Logs, screenshots, and evidence

pnpm install output: unmet peer @hocuspocus/provider@^3.4.0: found 4.8.0.

Maintainer Codex context

No response

Impact and severity

Packaging only: a warning on every install for anyone on Hocuspocus 4.x, and no signal from Plate whether v4 is supported. No editor breakage observed.

Additional information

No response