You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For .ts I understand, since the TypeScript compiler makes the same distinction, but why would we do this for .js files? There are plenty of codebases that use .js files with JSX content and it's an accepted practice.
It's an old and debatable practice. Nowadays, new projects always use .tsx and .jsx straightaway. New and modern projects should rely on file extensions and prior config, see .mjs and .cjs and pakcage.json#type, for example.
We intend to provide an option to opt in to the old behaviour (there's already a task for that in the checklist).
No description provided.
The text was updated successfully, but these errors were encountered: