When importing module with js extension also try to resolve corresponding module with tsx extension

[renke]

Clear and concise description of the problem

A similar functionality was already implemented in #5510 but the implementation only tries once to either resolve $module.ts or $module.tsx (depending on the extension used in the import).

TypeScript typecheck does not complain when using .js and there only exist a corresponding .tsx module. So Vite would behave closer to how TypeScript works when this would be implemented, following basically the same reasoning as in the aforementioned merged PR.

Suggested solution

Vite could also try to resolve a module using .tsx (instead of only .ts) even if the import uses just .js.

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[radoslavkarlik]

I have also encountered this when migrating a project to vite. Is there any workout currently?

[renke]

This seems to be no longer a problem as of version 2.9.0-beta.0. Thank you!