TypeScript refuses JSX because the jsx option is not set
Cannot use JSX unless the '--jsx' flag is provided.Short answer
TypeScript compiles JSX only when you name the file with a .tsx extension and enable the jsx compiler option. The error means the option is missing in the tsconfig that applies to the file. Set jsx to react-jsx for the modern React runtime, or preserve if a bundler transforms the JSX.
Fix it fast
1Find out which cause you have
Print the configuration TypeScript really uses, including values inherited with extends. If jsx is absent there, that is the cause.
npx tsc --showConfig | grep -n jsx2Match what you see, then jump to its fix
What does the error look like?
Cannot use JSX unless the '--jsx' flag is provided.TS17004: Cannot use JSX unless the '--jsx' flag is provided.
Cause 1 of 2
The jsx option is not set
1Check
Look in tsconfig.json and in every file it extends. A project-references setup can have the option in one config and not in the one that covers your file.
grep -rn "\"jsx\"" tsconfig*.json2Fix
Add jsx to compilerOptions. react-jsx emits the automatic-runtime calls and needs no React import in each file. preserve keeps the JSX for a later tool such as Babel or a bundler. react emits React.createElement.
{
"compilerOptions": {
"jsx": "react-jsx"
}
}3Verify
Restart the editor's TypeScript server and run the compiler.
npx tsc --noEmitConfirmed by typescriptlang.org
Cause 2 of 2
The file has a .ts extension
1Check
TypeScript's JSX guide lists two requirements: the .tsx extension and the jsx option. A .ts file cannot hold JSX.
grep -rln "</\|/>" src --include=*.ts2Fix
Rename the file to .tsx and update imports that name the extension, if any.
git mv src/Button.ts src/Button.tsx3Verify
Type-check again; the error is gone.
npx tsc --noEmitConfirmed by typescriptlang.org
How do I stop it coming back?
- Start new projects from a maintained template that already has jsx set.
- Set jsx in the base tsconfig that others extend, not in each child.
- Use the same value your bundler expects: preserve when it transforms JSX itself.
- Run tsc --noEmit in CI.
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 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 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