-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: React 19 global JSX namespace deprecation #569
Comments
Here's the diff I used to generate the above diffs
|
❯ git --no-pager diff --no-ext-diff -p
+"@types/react-dom@^19.0.0":
"@types/[email protected]": -"@types/react@", "@types/[email protected]", "@types/react@^18.0.0": +"@types/react@^19.0.0":
"@types/[email protected]": |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I don't think this should be marked stale - its an ongoing issue. Just commenting to count as activity. |
This is the only library in our project that holds us from upgrading to React 19. |
What happened?
As part of the React 19 release they've deprecated the JSX global namespace, in favour of React.JSX.Element. While y'all aren't explicitly using JSX.Element anywhere, it does it appear in the emitted type definition files, specifically:
The "easy" fix for this is to use React 19 in the package.json which shouldn't really cause any changes in your library. I had a little try at this locally and discovered the following diffs - ignoring the crappy one-liner to find all the diffs.
However,
yarn build
now fails due to the script/check-imports script. I'm not 100% sure what the plan with that is, so didn't want to make an pull request without understanding the goal of this script.Environment
No response
Reproduction
No response
The text was updated successfully, but these errors were encountered: