Skip to content

chore: upgrade @blocknote/* to 0.51 (frontend + hocuspocus) [feasibility]#23315

Draft
wielinde wants to merge 1 commit into
devfrom
chore/upgrade-blocknote-0.51
Draft

chore: upgrade @blocknote/* to 0.51 (frontend + hocuspocus) [feasibility]#23315
wielinde wants to merge 1 commit into
devfrom
chore/upgrade-blocknote-0.51

Conversation

@wielinde
Copy link
Copy Markdown
Member

⚠️ Feasibility study — DO NOT MERGE.
This PR is meant to show what the openproject-side consumer changes look like for the BlockNote 0.51 / op-blocknote-extensions 0.1.0 bump. It depends on opf/op-blocknote-extensions PRs #133 and #134, neither of which is merged or released yet, so the GitHub URLs for the new tgz don't resolve. Lockfiles are intentionally left untouched.

What this PR demonstrates

frontend/

  • @blocknote/{core,mantine,react}: ^0.44.2^0.51.0
  • op-blocknote-extensions: v0.0.26v0.1.0 (URL not live yet)
  • OpBlockNoteEditor.tsx: BlockNote 0.51 tightened CollaborationOptions — omit the whole collaboration block when no hocuspocusProvider is wired up; cast the provider at the boundary because Hocuspocus's awareness: Awareness | null doesn't match BlockNote's Awareness | undefined.

extensions/op-blocknote-hocuspocus/

  • @blocknote/server-util: ^0.44.2^0.51.0
  • @blocknote/core (dev): ^0.44.2^0.51.0
  • op-blocknote-extensions: v0.0.18v0.1.0
  • openProjectApi.ts: import the static specs from the new op-blocknote-extensions/server subpath (keeps @blocknote/react out of Node); align schema key with the post-refactor block type (openProjectWorkPackageopenProjectWorkPackageBlock); register the inline static spec so inline work-package chips survive markdown export.

Why feasibility-only right now

Treat the diff as the contract: this is roughly what the next real PR will commit once v0.1.0 ships.

Refs

🤖 Generated with Claude Code

… (FEASIBILITY)

Feasibility-study draft showing the openproject-side consumer changes
that go with op-blocknote-extensions v0.1.0 (opf/op-blocknote-extensions
PRs #133 and #134, not yet merged):

frontend
- @blocknote/{core,mantine,react}: ^0.44.2 → ^0.51.0
- op-blocknote-extensions: v0.0.26 → v0.1.0 (URL not live yet)
- OpBlockNoteEditor.tsx: BlockNote 0.51 tightened CollaborationOptions —
  omit the whole `collaboration` block when no hocuspocusProvider is
  wired up; cast the provider at the boundary because Hocuspocus's
  `awareness: Awareness | null` doesn't match BlockNote's
  `Awareness | undefined`.

hocuspocus (extensions/op-blocknote-hocuspocus)
- @blocknote/server-util: ^0.44.2 → ^0.51.0
- @blocknote/core (dev): ^0.44.2 → ^0.51.0
- op-blocknote-extensions: v0.0.18 → v0.1.0
- openProjectApi.ts: import the static specs from the new
  `op-blocknote-extensions/server` subpath (keeps @blocknote/react out
  of Node); align schema key with the post-refactor block type
  ("openProjectWorkPackage" → "openProjectWorkPackageBlock"); register
  the inline static spec so inline work-package chips survive the
  markdown export.

Lockfiles intentionally not regenerated: the v0.1.0 GitHub URL doesn't
resolve yet. Reviewers should treat this PR as a feasibility study, not
a mergeable artefact.

Refs: https://community.openproject.org/wp/74654

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant