Widget Primitives: make @types/react an optional peer dependency

[retrofox]

What?

Marks @types/react as an optional peer dependency of @wordpress/widget-primitives through peerDependenciesMeta.

Why?

@types/react is only useful to consumers that use TypeScript.

Marking it optional avoids an unmet-peer warning for plain-JavaScript consumers, and matches the convention already followed by other React packages.

Testing

Metadata-only change, with no runtime or test impact. After install, @types/react no longer reports as a missing peer for consumers that do not use TypeScript.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: retrofox <[email protected]>
Co-authored-by: manzoorwanijk <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Size Change: 0 B

Total Size: 8.6 MB

_{compressed-size-action}

[manzoorwanijk]

Thanks

[github-actions]

Flaky tests detected in 21dbe4b.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/27687382663
📝 Reported issues:

• [Flaky Test] Should save the changes #78689 in /test/e2e/specs/editor/plugins/wp-editor-meta-box.spec.js
• [Flaky Test] should not be possible to edit connected blocks #79216 in /test/e2e/specs/editor/various/block-bindings/post-meta.spec.js
• [Flaky Test] shouldn't conflict with server-side autosave #78706 in /test/e2e/specs/editor/various/autosave.spec.js