ESM strict imports mode option to moduleResolution bundler

🔍 Search Terms

moduleResolution bundler esm imports

✅ 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

Add an option to enforce imports with file extension when the module is iESM (type: module) and moduleResolution is bundler.

📃 Motivating Example

For now in bundler moduleResolution, typescript is tolerent.
But when we develop a library, we have no idea of the strictness of the bundler (webpack is strict for example).
We need a way to enforce the imports with file extension in case the module is ESM

A dedicated option in the tsconfig can resolve it that we will enable or not

💻 Use Cases

1. What do you want to use this for?
2. What shortcomings exist with current approaches?
3. What workarounds are you using in the meantime?

Commencez par examiner le comportement moduleResolution bundler du compilateur et sa gestion des imports ESM (type: module). Définissez comment l’option tsconfig proposée doit imposer les extensions de fichier sans modifier le comportement existant, puis ajoutez une couverture pour les configurations strict et non-strict. Le travail est terminé lorsque bundler resolution signale les imports ESM sans extension lorsque l’option est activée.