JSX Element, React Node, React Element
Muhammad Ridho Anshory
Posted on March 12, 2022
I am currently migrating a React application to TypeScript. So far, this works pretty well, but I have a problem with the return types of my render
functions, specifically in my functional components.
Cut a long story short, I have these questions during my learning process:
- What is the difference between
JSX.Element
,ReactNode
andReactElement
? - Why do the
render
methods of class components returnReactNode
, but functional components returnReactElement
?
What is the difference between JSX.Element
, ReactNode
and ReactElement
?
A ReactElement is an object with a type and props.
type Key = string | number
interface ReactElement<P = any, T extends string | JSXElementConstructor<any> = string | JSXElementConstructor<any>> {
type: T;
props: P;
key: Key | null;
}
A ReactNode is a ReactElement, a ReactFragment, a string, a number or an array of ReactNodes, or null, or undefined, or a boolean:
A ReactNode is a ReactElement, a ReactFragment, a string, a number or an array of ReactNodes, or null, or undefined, or a boolean:
type ReactText = string | number;
type ReactChild = ReactElement | ReactText;
interface ReactNodeArray extends Array<ReactNode> {}
type ReactFragment = {} | ReactNodeArray;
type ReactNode = ReactChild | ReactFragment | ReactPortal | boolean | null | undefined;
JSX.Element is a ReactElement, with the generic type for props and type being any. It exists, as various libraries can implement JSX in their own way, therefore JSX is a global namespace that then gets set by the library, React sets it like this:
declare global {
namespace JSX {
interface Element extends React.ReactElement<any, any> { }
}
}
By example:
<p> // <- ReactElement = JSX.Element
<Custom> // <- ReactElement = JSX.Element
{true && "test"} // <- ReactNode
</Custom>
</p>
Why do the render
methods of class components return ReactNode
, but functional components return ReactElement
?
they do return different things. Components
return:
render(): ReactNode;
tl;dr: It is a current TS type incompatibility not related to core React.
- TS class component: returns
ReactNode
withrender()
, more permissive than React/JS - TS function component: returns
JSX.Element | null
, more restrictive than React/JS
In principle, render()
in React/JS class components supports the same return types as a function component. With regard to TS, the different types are a type inconsistency still kept due to historical reasons and the need for backwards compatibility.
Ideally a valid return type would probably look more like this:
type ComponentReturnType = ReactElement | Array<ComponentReturnType> | string | number
| boolean | null // Note: undefined is invalid
If you guys have other thoughts leave a comment I'll update the post base on your solutions as well.. cheers🍻
Posted on March 12, 2022
Join Our Newsletter. No Spam, Only the good stuff.
Sign up to receive the latest update from our blog.