Make React
import fix not block component import fix
#50307
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
“Fixes” #50192
There’s been a lot of confusion lately about whether an import of
React
is needed in JSX files under different JSX compilers, and how to configure TypeScript to recognize that requirement or lack thereof. Historically, if TypeScript thought that aReact
import was needed, auto-imports would only offer to importReact
on JSX opening tags, even if the local component name also needed to be imported.Before:
After:
Users should still configure TS to get rid of that error if it doesn’t apply to their build system, but hopefully making both auto-imports available will make the misconfiguration a bit less painful, especially for plain-JS VS Code users who are just getting default settings and don’t know where they’re coming from.