fix: align react peerDependencies across react-components packages

[Martin Hochel (Hotell)]

Previous Behavior

Peer dependency ranges for react, react-dom, @types/react and @types/react-dom had drifted into 5 different signatures across publishable packages/react-components/** packages, 12 of which were internally incoherent:

Count	react	react-dom	@types/react	@types/react-dom
58	>=16.14.0	>=16.14.0	>=16.14.0	>=16.9.0	✅ canonical
5	>=16.14.0	—	>=16.14.0	—	✅ non-DOM packages
7	>=16.14.0	>=16.8.0	>=16.8.0	>=16.8.0	❌
2	>=16.8.0	>=16.14.0	>=16.14.0	>=16.9.0	❌
3	>=16.8.0	>=16.8.0	>=16.8.0	>=16.8.0	❌ transitively unsatisfiable

Every v9 package depends on @fluentui/react-jsx-runtime, which does a hard module import of react/jsx-runtime:

// packages/react-components/react-jsx-runtime/src/utils/Runtime.ts
import * as ReactRuntime from 'react/jsx-runtime';

That entry point was only backported to the 16.x line in react@16.14.0 — verified by unpacking both tarballs:

react@16.13.1 -> 0 jsx-runtime files
react@16.14.0 -> package/jsx-runtime.js
                 package/cjs/react-jsx-runtime.development.js
                 package/cjs/react-jsx-runtime.production.min.js

So react >=16.14.0 is a hard floor. Any package advertising >=16.8.0 lets a consumer on React 16.8–16.13 install cleanly and then fail to resolve react/jsx-runtime at build/runtime.

How the skew happened

1. 400cd5a243 — a bad release run wrote the package's own version into peers: "react": "^8.119.0", across ~97 package.json files.
2. fix: revert incorectly set react versions in all packages #31937 (4edb54ea6e) reverted it — but restored only the react key, hand-assigning >=16.14.0 to 63 entries and >=16.8.0 to the rest. react-dom, @types/react and @types/react-dom were left untouched at whatever they had. This is the origin of the mismatch.
3. chore: extend packages peer dependencies versions to support React 19 #35145 (eb7f6d51c2) added React 19 support via a mechanical <19.0.0 → <20.0.0 sweep. It preserved lower bounds verbatim, freezing the skew in place — and it never touched tools/, leaving the generator template stale.

New Behavior

All publishable packages/react-components/** packages collapse to one signature:

"@types/react":     ">=16.14.0 <20.0.0",
"@types/react-dom": ">=16.9.0 <20.0.0",
"react":            ">=16.14.0 <20.0.0",
"react-dom":        ">=16.14.0 <20.0.0"

@types/react-dom intentionally stays at >=16.9.0: no 16.14.x was ever published for it (16.x ends at 16.9.25), which is exactly what #30259 fixed. Every other package keeps >=16.14.0.

12 packages normalized: react-infolabel, react-list, react-message-bar, react-motion, react-rating, react-swatch-picker, react-teaching-popover, react-datepicker-compat, react-migration-v8-v9, react-calendar-compat, react-icons-compat, react-timepicker-compat

The 5 non-DOM packages (react-utilities, react-jsx-runtime, react-shared-contexts, react-portal-compat, react-portal-compat-context) correctly declare no react-dom peer and were already canonical — untouched.

Generator template fixed: tools/workspace-plugin/src/generators/react-library/files/package.json__tmpl__ still emitted <19.0.0, so every package scaffolded since #35145 started life with a stale upper bound.

This is metadata-only — no source, build output or runtime behavior changes. It narrows an advertised range that was never actually supported, so no consumer on a working configuration is affected.

Validation

• beachball check → clean (12 patch change files, one per changed package)
• nx run workspace-plugin:test --testPathPatterns=react-library → 3 tests, 10 snapshots passed
• prettier --check → clean

Follow-up (not in this PR)

Nothing prevents this from drifting again — normalize-package-dependencies only validates internal workspace deps and deliberately skips external peers. A coherence check for the four react peers would make this regression-proof. Happy to add it here or in a separate PR.

Related Issue(s)

• Follows up on fix: revert incorectly set react versions in all packages #31937, chore: extend packages peer dependencies versions to support React 19 #35145, Revert peer dep for types/react-dom which asked for a 16.x version that has not been released #30259

[github-actions]

📊 Bundle size report

✅ No changes found

[github-actions]

Pull request demo site: URL