React error Type '() => JSX.Element[]' is not assignable to type FunctionComponent
When we try to return an array of elements from a function component, a React.js error “Type '() => JSX.Element[]' is not assignable to type FunctionComponent” occurs. To fix this error, you need to wrap the array of elements in a React fragment.
Below is an example of where the error occurs.
import React from 'react';
// ⛔️ Type '() => JSX.Element[]' is not assignable to type 'FunctionComponent<{}>'.
// Type 'Element[]' is missing the following properties
// from type 'ReactElement<any, any>': type, props, key ts(2322)
const App: React.FunctionComponent = () => {
return ['Alice', 'Bob'].map(element => <div key={element}>{element}</div>);
};
export default App;
This is perfectly valid React.js code, as we should be able to return an array from a function component in React. However, the return type of the FunctionComponent interface is either ReactElement or null.
This means we can only return a React element or a null value.
To avoid type errors, we have to wrap the array in a React fragment
import React from 'react';
const App: React.FunctionComponent = () => {
return (
<>
{['Alice', 'Bob'].map(element => (
<div key={element}>{element}</div>
))}
</>
);
};
export default App;
Fragments are used when we need to group a list of elements without adding extra nodes to the DOM.
We may also see a more verbose snippet syntax being used.
import React from 'react';
const App: React.FunctionComponent = () => {
return (
<React.Fragment>
{['Alice', 'Bob'].map(element => (
<div key={element}>{element}</div>
))}
</React.Fragment>
);
};
export default App;
The two examples above achieve the same result—they group a list of elements without adding extra nodes to the DOM.
Another solution is to wrap the array of elements in another DOM element, such as a div
.
import React from 'react';
const App: React.FunctionComponent = () => {
return (
<div>
{['Alice', 'Bob'].map(element => (
<div key={element}>{element}</div>
))}
</div>
);
};
export default App;
This still complies with the return type specified in the FunctionComponent interface, since our component returns a single React element.
For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.
Related Articles
Fix Uncaught ReferenceError: useState is not defined in React
Publish Date:2025/03/15 Views:142 Category:React
-
When we use the useState hook in our code but forget to import it, it generates the error Uncaught ReferenceError: useState is not defined. To fix this error, you need to import the hook before using it import {useState} from react . // ?️
React error Uncaught ReferenceError: process is not defined solution
Publish Date:2025/03/15 Views:116 Category:React
-
要解决 React 中的“Uncaught ReferenceError: process is not defined” 错误,需要在项目的根目录中打开终端并通过运行 `npm install react-scripts@latest` 更新 `react-scripts` 包的版本,并在必要时重新安装
How to solve the "Function components cannot have string refs" error in React
Publish Date:2025/03/15 Views:138 Category:React
-
当我们在函数组件中使用字符串作为引用时,会出现错误“Function components cannot have string refs”。 要解决该错误,需要使用 useRef() 钩子来获取一个可变的 ref 对象,我们可以将其用作组件
React Error Property 'X' does not exist on type 'Readonly<{}>'
Publish Date:2025/03/15 Views:139 Category:React
-
当我们尝试访问未键入的类组件的 props 或状态时,会发生 React.js 错误“Property does not exist on type 'Readonly '”。 要解决该错误,需要使用 React.Component 类上的泛型来输入该类的道具或状
Solve React's Unexpected default export of anonymous function error
Publish Date:2025/03/15 Views:119 Category:React
-
当我们尝试使用默认导出导出匿名函数时,会导致“Unexpected default export of anonymous function”警告。 要解决此错误,需要在导出函数之前为其命名。
How to solve React Type {children: Element} has no properties in common with type
Publish Date:2025/03/15 Views:103 Category:React
-
React.js error "Type {children: Element} has no properties in common with type IntrinsicAttributes" occurs when we try to pass children prop to a component without any props. To resolve the error, you need to define and type the properties on the comp
Fix the value prop on input should not be null error in React
Publish Date:2025/03/15 Views:141 Category:React
-
The warning "value prop on input should not be null" is caused when we set the initial value of an input to null or override the initial value setting it to null, e.g. from an empty API response. Use a fallback value to solve this problem.
Property does not exist on type 'JSX.IntrinsicElements' error in React
Publish Date:2025/03/15 Views:188 Category:React
-
When the name of a component starts with a lowercase letter, an error "Property does not exist on type 'JSX.IntrinsicElements" will appear. To fix this error, you need to make sure you always start your component names with an uppercase letter, instal
React uses Router to get the current route
Publish Date:2025/03/15 Views:99 Category:React
-
Use the `useLocation()` hook to get the current route through React Router, such as `const location = useLocation()`. The hook returns the current location object. For example, we can access the pathname as location.pathname.