TypeScript rejects a component that returns an array or other non-Element
'List' cannot be used as a JSX component.Short answer
TypeScript before 5.1 required every component to return JSX.Element or null, so arrays, strings and Promises were rejected even though React renders them. Upgrade TypeScript to 5.1 or newer, together with a current @types/react, or wrap the returned array in a Fragment so the component returns one element.
Fix it fast
1Find out which cause you have
Check the TypeScript version the project and the editor use. The check changed in 5.1, so an older compiler explains the error.
npx tsc --version && npm ls typescript @types/react2Match what you see, then jump to its fix
What does the error look like?
'List' cannot be used as a JSX component.Its return type 'Element[]' is not a valid JSX element.Its return type 'Promise<Element>' is not a valid JSX element.
Cause 1 of 2
TypeScript is older than 5.1
1Check
Before 5.1 every JSX tag had to be compatible with JSX.Element. Version 5.1 looks up JSX.ElementType instead, which lets the types package say what is valid as a tag.
npx tsc --version2Fix
Upgrade TypeScript, and make sure the editor uses the workspace copy and not a bundled older one.
npm install --save-dev typescript@latest3Verify
Run the type check; the error disappears for the same file.
npx tsc --noEmitConfirmed by typescriptlang.org
Cause 2 of 2
The component returns an array and you cannot upgrade yet
1Check
Find the component whose body returns items.map(...) directly.
grep -rn "return .*\.map(" src/2Fix
Wrap the result in a Fragment. A Fragment groups elements into one value and adds no DOM node. When each item is itself a Fragment, use the explicit Fragment tag with a key.
function List({ items }: { items: Item[] }) {
return (
<>
{items.map(i => <Row key={i.id} item={i} />)}
</>
);
}3Verify
Run the type check, then render the component in the browser.
npx tsc --noEmitConfirmed by react.dev
How do I stop it coming back?
- Keep TypeScript and @types/react on current versions, and update them together.
- Install one copy of @types/react only; check with npm ls @types/react.
- Have the editor use the workspace TypeScript version.
- Return a Fragment when a component renders a list at its top level.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
TypeScript refuses JSX because the jsx option is not set
TS17004: Cannot use JSX unless the '--jsx' flag is provided.
TypeScript compiles JSX only when you name the file with a .tsx extension and enable the jsx compiler option.
2 causes, each with a fixWeb apps
ESLint says it cannot resolve a path to a module that does exist
Unable to resolve path to module 'react'. import/no-unresolved
import/no-unresolved fails when eslint-plugin-import cannot find the file or package on disk with its resolver.
4 causes, each with a fixWeb apps
ESLint reports no-unused-vars for React components and imports that are used
no-unused-vars reported for a component that is rendered as a JSX tag
ESLint's core no-unused-vars does not see variables used only as JSX tags, so a component imported and rendered as <Hello /> looks unused.
3 causes, each with a fixWeb apps
TypeScript rejects MUI Data Grid columns that set a type
A TypeScript error inside a column's renderCell callback
A columns array declared without a type is inferred with type as a plain string, which the Data Grid's column type union does not accept.
2 causes, each with a fixWeb apps
The renderInput prop stopped working on the MUI X DatePicker
The custom TextField (variant, size, helperText) is ignored
renderInput was removed from the MUI X date pickers in version 6.
3 causes, each with a fixWeb apps
Upgrading to Next.js 16: middleware becomes proxy, and the other things that break
Missing Required default.js for Parallel Route
Next.js 16 renames middleware.ts to proxy.ts and its exported function to proxy.
6 causes, each with a fix