`--jsx react` should be deemphasized

[eps1lon]

🔍 Search Terms

React, JSX

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

When suggesting a JSX option, react should be deemphasized since it's the old runtime that has been superseded by the new, automatic runtime.

📃 Motivating Example

tsc index.tsx --jsx
error TS6044: Compiler option 'jsx' expects an argument.
error TS6046: Argument for '--jsx' option must be: 'preserve', 'react-native', 'react', 'react-jsx', 'react-jsxdev'.

💻 Use Cases

1. What do you want to use this for?
   Nudge people to use new, automatic transform
2. What shortcomings exist with current approaches?
   Seems to prioritize react over react-jsx
3. What workarounds are you using in the meantime?
   None