microsoft / microsoft/TypeScript
[BUG] This JSX tag requires the module path 'react/jsx-runtime' to exist, but none could be found. Make sure you have types for the appropriate package installed.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.100.23258
- OS Version: Linux x64 6.9.3-76060903-generic
- Chromium: 132.0.6834.210
- Node.js: 20.19.0
- V8: 13.2.152.41-electron.0
Steps to Reproduce:
1. Open a .tsx file in a solidjs project (probably any non-react project) and observe all JSX syntax triggers a typescript error masking other potential ts errors.

- 1.100 always happens and the error changed to `This JSX tag requires the module path 'react/jsx-runtime' to exist, but none could be found. Make sure you have types for the appropriate package installed.` See [merge](https://github.com/microsoft/vscode/pull/246738)
Prior versions showed up like this:
- 1.95.3
- 1.98.2.25078 it occasionally happened but the error was `"This JSX tag requires 'React' to be in scope, but it could not be found."`

A work-around is appreacted!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the diagnostic in a .tsx file within a SolidJS project, with extensions disabled, and compare the behavior across the reported VS Code and TypeScript versions. Trace the JSX type-checking path that produces the react/jsx-runtime requirement; done means valid SolidJS JSX no longer receives this misleading diagnostic while other TypeScript errors remain visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100