TypeScript reads a React context provider as a type, not as JSX
Cannot find namespace 'ctx'Short answer
TypeScript only parses JSX in files named .tsx, and only when the jsx compiler option is set. In a .ts file the JSX is not parsed as JSX, which is how a name like ctx ends up reported as a missing namespace. Rename the file to .tsx and set jsx to react-jsx in tsconfig.json.
Fix it fast
1Find out which cause you have
Look at the extension of the file that holds the JSX, and at the jsx line in tsconfig.json.
ls src/context/ grep -n "\"jsx\"" tsconfig*.json2Match what you see, then jump to its fix
What does the error look like?
Cannot find namespace 'ctx'the same context code compiles when the file is named .tsx
Cause 1 of 2
The file that contains JSX is named .ts
1Check
The TypeScript handbook gives two requirements for JSX: name the file with a .tsx extension, and enable the jsx option. A .ts file does not get JSX parsing, so the markup around ctx.Provider is not understood.
ls src/context/*.ts | xargs grep -ln "<.*Provider"2Fix
Rename the file to .tsx and update the imports if they spell the extension.
git mv src/context/AppContext.ts src/context/AppContext.tsx3Verify
Restart the type checker. The namespace error is gone.
npx tsc --noEmitConfirmed by typescriptlang.org
Cause 2 of 2
The jsx compiler option is not set in tsconfig.json
1Check
Without the jsx option, TypeScript refuses JSX even in .tsx files. The tsconfig reference lists the values preserve, react, react-native, react-jsx and react-jsxdev.
grep -n "\"jsx\"" tsconfig.json tsconfig.app.json 2>/dev/null2Fix
Set jsx in the compilerOptions that apply to your source files. The react-jsx value uses the automatic runtime, so you do not need to import React in each file.
{
"compilerOptions": {
"jsx": "react-jsx"
}
}3Verify
Run the type checker again.
npx tsc --noEmitConfirmed by typescriptlang.org
How do I stop it coming back?
- Name every file that contains JSX with .tsx, and keep plain logic in .ts.
- Use as for type assertions: the handbook says angle bracket assertions are not allowed in .tsx files.
- Create new React projects from a current template, which sets jsx for you.
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