Conversation
|
What do you think about |
|
The problem with I can see why it makes more sense to be agnostic but I don't think |
…transform Deemphasize old JSX transform
|
Possibly related: I'm using solidjs and mostly it is usually fine without this error. But after moving files around, the editor occasionally gets hung up on |
|
That seems unrelated to this change considering that error is the one you get with the previous defaults. The new default would not trigger this error since |
The old JSX transform requires a React import so you get a "This JSX tag requires 'React' to be in scope, but it could not be found.ts(2874)" for files without a tsconfig in VSCode by default.
However, the default nowadays is the new, automatic JSX transform in React which doesn't need a React import so VSCode should default to that.
Related:
compilerOptions.jsxto reflect latest preferences TypeScript-Website#2994