React 19 support ☂️

[tay1orjones]

This issue is a high level catch-all for items relating to React 19 support.

As of April 25 React 19 is in beta. There's also an upgrade guide.

Steps to explore React 19 support

Preview Give feedback

1. Test against older versions of React #14350
   0 of 2
   proposal: not pursuing +1
2. Test against react@next #13610
   package: @carbon/react proposal: accepted role: dev 🤖 type: enhancement 💡 type: infrastructure 🤖 +5
3. The output of the above ^^ would be a failing ci check testing React 19 compatibility (unit tests, etc) and the work here would be to get that status check passing.
4. Get a React 19 branch set up for testing
5. Add React 19 as an allowed version in package.json(s)
6. Follow the 19 upgrade guide, resolve any incompatibilities in a backwards compatible way
7. ...
8. Once things feel solid, open a draft PR.
9. There may be further changes during the beta period. Work to keep this draft PR passing during the beta period.
10. Coordinate React 19 support within @carbon/ibm-products to land this at the same time
11. Merge the PR once React 19 lands in stable (or we could merge it asap if we leave out the changes to package.json. This would mean that the CI checks would need to support testing in versions of react that are not specified in our package.json - Test against react@next #13610
12. [Bug]: (Tabs) React 19 not rendering TabList items #16620
    role: dev 🤖 severity: 2 type: bug 🐛 +3

Open questions

• Can we support React 19 alongside 16, 17, and 18?
• Are we using anything that's been deprecated?
• Are we using anything that will be impacted by breaking changes?

[sstrubberg]

Can we align this body of work with the Product PAL? I would love to have this work be done in tandem across squads. @kennylam @matthewgallo @elycheea

[tay1orjones]

@sstrubberg totally agree, I just updated the tasklist to reflect that as a distinct item to address