[core] Apply React 19 type changes that don't require upcoming @types/
packages
#42346
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on #42032
First step towards #42032
Summary
This PR includes the type changes we can implement without upgrading to the new
@types/
packages (which is a WIP). It's achieved by:npx types-react-codemod@latest preset-19
but skipping theuseRef-required-initial
codemod (See missing section below)npx types-react-codemod@latest react-element-default-any-props
to maintainReactElement
's previous default.This results in the following changes:
JSX
usage in favor ofReact.JSX
ReactElement<any>
to retain the previous defaultMissing
The following are missing, to be implemented after DefinitelyTyped/DefinitelyTyped#69022 is merged:
useRef-required-initial
codemod yet. This is because it will be much easier with the newuseRef(undefined)
overload that's coming.npx types-react-codemod@latest react-element-default-any-props
is provided, it is discouraged. We should eventually fix them to work with theunknown
default.@emotion/react@11.11.4
references deprecated global JSX namespace. They mention they'll work on it once React 19 is released. We could look into contributing to it.