-
-
Notifications
You must be signed in to change notification settings - Fork 884
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
React 19 support #877
Comments
Hi! This was marked as ready to be worked on! Note that while this is ready to be worked on, nothing is said about priority: it may take a while for this to be solved. Is this something you can and want to work on? Team: please use the |
@wooorm If I upgrade to React 19 in this repo and
In syntax-tree/hast-util-to-jsx-runtime@ae638ba you provide the solution of declaring a global JSX namespace. Would you recommend doing that here? |
I tried the global JSX namespace suggestion import type { JSX as Jsx } from "react/jsx-runtime";
declare global {
namespace JSX {
type ElementClass = Jsx.ElementClass;
type Element = Jsx.Element;
type IntrinsicElements = Jsx.IntrinsicElements;
}
} ... but it doesn't seem to make a difference for the error I'm getting with React 19:
|
Actually, this suggestion worked for me. Upgraded to Next.js 15 and React 19 without errors. |
Followup to #871
react-markdown
relies onJSX
being in the global namespace, which has been removed in@types/react^19
.Per @ChristianMurphy here:
React 19 is now GA, so this issue is to track.
The text was updated successfully, but these errors were encountered: