Component cannot be used as a JSX component error in React
There are several reasons why the error “Component cannot be used as a JSX component” appears:
- Returns an array of JSX elements instead of a single element.
- Return any value other than a JSX element or null from a component.
- React typings with outdated versions.
Here is an example that produces the above error
// ⛔️ 'App' cannot be used as a JSX component.
// Its return type 'Element[]' is not a valid JSX element.
// Type 'Element[]' is missing the following properties from type 'ReactElement<any, any>': type, props, key
const App = () => {
return ['a', 'b', 'c'].map(element => {
return <h2 key={element}>{element}</h2>;
});
};
export default App;
The problem is that we're returning an array of JSX elements, not a single JSX element.
To fix this error, we have to
div
wrap the array using a React fragment or a <div> element.
const App = () => {
return (
<>
{['a', 'b', 'c'].map(element => {
return <h2 key={element}>{element}</h2>;
})}
</>
);
};
export default App;
Now our component returns a single JSX element, so the error is resolved.
Fragments are used when we need to group sublists without adding extra nodes to the DOM.
We may also see a more verbose snippet syntax used.
import React from 'react';
const App = () => {
return (
<React.Fragment>
{['a', 'b', 'c'].map(element => {
return <h2 key={element}>{element}</h2>;
})}
</React.Fragment>
);
};
export default App;
We can also use a wrapper div element to return a single JSX element from your component.
Another common cause of the “Component cannot be used as a JSX component” error is when we return anything other than a JSX element or null from a component, or forget to return a value.
// ⛔️ 'App' cannot be used as a JSX component.
// Its return type 'undefined' is not a valid JSX element.
const App = () => {
// 👇️ this returns undefined
return
<h2>hello world</h2>
};
export default App;
The App component returns undefined
because we put the return statement on one line and the JSX code on the next line without using brackets.
We are not allowed to return from a component
undefined
, so the error occurs.
To resolve this error, make sure the code we return is accessible.
const App = () => {
return (
<div>
<h2>hello world</h2>
</div>
);
};
export default App;
If we are sure to return a single JSX element or null from our React component but the error persists, try updating our React types.
Open a terminal in the root directory of your project (where your package.json file is located) and run the following command:
# 👇️ 使用 NPM
$ npm install --save-dev @types/react@latest @types/react-dom@latest
# 👇️ 如果你还想更新 react 和 react-dom
$ npm install react@latest react-dom@latest
# ------------------------------
# 👇️ 使用 YARN
$ yarn add @types/react@latest @types/react-dom@latest --dev
# 👇️ 如果你还想更新 react 和 react-dom
$ yarn add react@latest react-dom@latest
This command will update our version of React typings.
Make sure to restart the development server and IDE if necessary. The development server will not pick up changes until we stop and rerun
npm start
the command.
If the error is not resolved, try deleting the node_modules and package-lock.json (not package.json) files, re-running npm install
and restarting the IDE.
# 👇️ delete node_modules and package-lock.json
$ rm -rf node_modules
$ rm -f package-lock.json
$ rm -f yarn.lock
# 👇️ clean npm cache
$ npm cache clean --force
$ npm install
If the error persists, make sure to restart the IDE and the development server. VSCode often crashes and sometimes restarting can fix the problem.
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
How to avoid cross-origin (CORS) issues in React/Next.js
Publish Date:2025/03/17 Views:166 Category:NETWORK
-
In this article, we will introduce how to avoid cross-origin (CORS) issues in React/Next.js. Cross-origin resource sharing (CORS) is a protocol that defines how web requests should be handled when crossing different URLs.
React Tutorial - Transferring Props
Publish Date:2025/03/16 Views:185 Category:React
-
React transfers Props. Props are generated when components are encapsulated. Components expose some properties (Props) to the outside world to complete some functions.
React Tutorial: Props Anti-Pattern
Publish Date:2025/03/16 Views:183 Category:React
-
React's Props anti-pattern, using Props to generate state in getInitialState is an anti-pattern - Anti-Pattern.
React Tutorial - Props Validation
Publish Date:2025/03/16 Views:99 Category:React
-
Props validation is a very useful way to use components correctly. It can avoid many bugs and problems as your application becomes more and more complex. In addition, it can make your program more readable.
React tutorial: Types of Props for child components
Publish Date:2025/03/16 Views:170 Category:React
-
Usually, the child components of a React component are a group, that is, the child components are an array. Introduction to Type of the Children Props.
How to solve the error Uncaught TypeError: Cannot read properties of undefined in
Publish Date:2025/03/16 Views:150 Category:React
-
In the process of React development, we often encounter some errors. Here we look at an error reported in App.js. The error is as follows: App.js:69 Uncaught TypeError: Cannot read properties of undefined (reading 'setState') at onInput
Why do you need to bind event handlers in React Class Components?
Publish Date:2025/03/16 Views:58 Category:React
-
When using React, we must have come across control components and event handlers. We need to use `.bind()` in the constructor of the custom component to bind these methods to the component instance. As shown in the following code:
Solution to the error "does not contain a default export" in React
Publish Date:2025/03/16 Views:187 Category:React
-
When we try to use `default import` to import from a module that does not have a `default export`, we get a "does not contain a default export" error. To fix the error, make sure the module has named exports and wrap the import in curly braces, e.g.
Error in React: Attempted import error 'X' is not exported from Solution
Publish Date:2025/03/16 Views:76 Category:React
-
In React, the error “Attempted import error 'X' is not exported from” in React.js occurs when we try to import a named import that does not exist in the specified file. To fix the error, make sure the module has named exports and you have not obfu