TypeScript reports JSX elements as type any in a React project
JSX element implicitly has type 'any'Short answer
TypeScript finds the types of JSX tags in the React type package. The error means those types are missing or not wired in. Install @types/react, set the jsx option in tsconfig.json, keep JSX in .tsx files, and in React 19 move custom JSX typings inside declare module react.
Fix it fast
1Find out which cause you have
See whether the React type packages are installed and what the jsx option says.
npm ls @types/react @types/react-dom grep -n "\"jsx\"" tsconfig*.json2Match what you see, then jump to its fix
- 1
npm ls shows no @types/reactThe React type definitions are not installedFix - 2
grep finds no jsx entryThe jsx option is not set in tsconfig.jsonFix - 3
The error appears in a .ts fileThe file containing JSX is not a .tsx fileFix - 4
A global.d.ts declares namespace JSX with custom element names; the error began after upgrading to React 19A custom JSX declaration no longer fits React 19Fix
- 1
What does the error look like?
JSX element implicitly has type 'any'Tags such as div or span are underlined in red inside a .tsx file
Cause 1 of 4
The React type definitions are not installed
1Check
TypeScript learns what div, span and other tags accept from the React types.
npm ls @types/react2Fix
Install both type packages as dev dependencies.
npm install --save-dev @types/react @types/react-dom3Verify
Run the type check.
npx tsc --noEmitConfirmed by react.dev
Cause 2 of 4
The jsx option is not set in tsconfig.json
1Check
To use JSX, TypeScript needs the jsx compiler option enabled.
grep -n "jsx" tsconfig.json2Fix
Set it to react-jsx for the automatic runtime, or to preserve when a bundler handles JSX after TypeScript.
{
"compilerOptions": {
"jsx": "react-jsx"
}
}3Verify
Run the type check again.
npx tsc --noEmitConfirmed by typescriptlang.org
Cause 3 of 4
The file containing JSX is not a .tsx file
1Check
Every file with JSX needs the .tsx extension.
grep -rln "</" src --include=*.ts2Fix
Rename the file and update imports that name the extension.
git mv src/Button.ts src/Button.tsx3Verify
Check types.
npx tsc --noEmitConfirmed by react.dev
Cause 4 of 4
A custom JSX declaration no longer fits React 19
1Check
React 19 removed the global JSX namespace in favour of React.JSX. A declaration that only defines some intrinsic elements makes other names an error.
grep -rn "namespace JSX" src *.d.ts2Fix
Put the augmentation inside declare module react, and use React.JSX.Element where the global JSX type was used.
// global.d.ts
declare module "react" {
namespace JSX {
interface IntrinsicElements {
"my-element": { myElementProps: string };
}
}
}3Verify
Run the type check.
npx tsc --noEmitConfirmed by react.dev
How do I stop it coming back?
- Create projects from the official templates, which set jsx and install the React types.
- Keep @types/react on the same major version as react.
- Run the React 19 types codemod when upgrading a TypeScript project.
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
TypeScript rejects a component that returns an array or other non-Element
Its return type 'Element[]' is not a valid JSX element.
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.
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 fix