These are two distinct issues. I created a small playground to show what means what. I hope this clarifies why

1. It’s technically incorrect to keep the line export as namespace React for React 19.
2. This syntax is purely stylistic and could be changed in a patch version:

   export = React
   namespace React {
     // …
   }

This syntax is purely stylistic and could be changed in a patch version

PRs welcome.

It’s technically incorrect to keep the line export as namespace React for React 19.

I don't think it was ever correct. You shouldn't magically get access to a global React. But a lot of the ecosystem relies on this. This needs an owner that pushes this end-to-end (DT PR, codemod, fixing all @types/ packages before we land etc).

Hello, is this removal still planned for React 20. If so, I assume the recommended approach in React 20+ is to explicitly type the children prop as children?: React.ReactNode, correct? Thanks.

Cheers

I personally would lint against usage. But it's a pretty big breaking change and hard to codemod in a desired way. You should just avoid the intersection since intersections aren't free. I suspect people will just reintroduce the type internally.

The event handlers issue needs more investigation. Events bubble so just because a div might not be the target of a canplay event doesn't mean that the canplay event doesn't propagate through it.

You’re right about the event propagation. I was under the impression React prevented event bubbling for some reason, but I was wrong.