It appears that `@wordpress/block-editor@15.0.0` is not compatible with `react@19.1.1`.

[stein2nd]

Description

When @wordpress/block-editor@15.0.0 is additionally installed on a project that has react@19.1.1 installed, an error is displayed.

Step-by-step reproduction instructions

1. Prepare a project folder (plugin) for testing.
2. Run npm install react react-dom and run npm install -D @types/react @types/react-dom.
3. Run npm install -D @wordpress/block-editor @types/wordpress__block-editor.

Screenshots, screen recording, code snippet

Environment info

System:

• OS: macOS 15.6
• CPU: (10) arm64 Apple M4
• Memory: 387.22 MB / 24.00 GB
• Shell: 5.9 - /bin/zsh

Binaries:

• Node: 24.5.0 - ~/.nvm/versions/node/v24.5.0/bin/node
• Yarn: 1.22.19 - ~/.nvm/versions/node/v24.5.0/bin/yarn
• npm: 11.5.2 - ~/.nvm/versions/node/v24.5.0/bin/npm
• pnpm: 8.6.12 - ~/.nvm/versions/node/v24.5.0/bin/pnpm

npmPackages:

• @types/node: ^24.2.0 => 24.2.0
• @types/react: ^19.1.9 => 19.1.9
• @types/react-dom: ^19.1.7 => 19.1.7
• @types/wordpress__block-editor: ^11.5.17 => 11.5.17
• @types/wordpress__blocks: ^12.5.18 => 12.5.18
• @types/wordpress__element: ^2.14.1 => 2.14.1
• @vitejs/plugin-react: ^4.7.0 => 4.7.0
• @wordpress/block-editor: ^15.0.0 => 15.0.0
• @wordpress/blocks: ^15.0.0 => 15.0.0
• @wordpress/element: ^6.27.0 => 6.27.0
• @wordpress/i18n: ^6.0.0 => 6.0.0
• eslint: ^9.32.0 => 9.32.0
• prettier: ^3.6.2 => 3.6.2
• react: ^19.1.1 => 19.1.1
• react-dom: ^19.1.1 => 19.1.1
• sass: ^1.89.2 => 1.89.2
• stylelint: ^16.23.0 => 16.23.0
• stylelint-scss: ^6.12.1 => 6.12.1
• typescript: ^5.9.2 => 5.9.2
• vite: ^7.0.6 => 7.0.6

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

• Yes

Please confirm which theme type you used for testing.

• Block
• Classic
• Hybrid (e.g. classic with theme.json)
• Not sure

[Mamaduka]

Unfortunately, there are some known issues with the React 19 upgrade. See: #61521.

I'm going to close this issue, since it's not actionable separately. Please subscribe to the linked PR updates.