Add allowImportingJsExtensions option to prevent incorrect .js imports

🔍 Search Terms

moduleResolution nodenext, import js extension, prevent .js imports, strict module resolution

✅ 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

Introduce a new compiler option:

"allowImportingJsExtensions": false

When set to false, TypeScript should prevent importing .js extensions unless the corresponding .js file physically exists.

Currently, in projects using "moduleResolution": "nodenext", TypeScript allows importing .js extensions even when there is no actual .js file, leading to confusion and incorrect imports in TypeScript-only projects.

📃 Motivating Example

Consider a TypeScript project using "moduleResolution": "nodenext":

import { something } from "./utils.js"; // Allowed, but utils.js does not exist

Here, TypeScript does not raise an error even though utils.js is not present. This can cause issues in projects that exclusively use .ts files and never generate .js files manually.

With the proposed option:

"allowImportingJsExtensions": false

The above import would result in a TypeScript error unless utils.js is physically present.

💻 Use Cases

1. Prevent incorrect imports in TypeScript-only projects: This option helps ensure .js imports are only allowed when the actual file exists, reducing accidental misconfigurations.
2. Stricter enforcement of module resolution: This aligns with "moduleResolution": "nodenext", enforcing explicit file extensions while avoiding implicit assumptions.
3. Avoid runtime errors: Developers may assume a .js file exists due to TypeScript allowing the import, only to discover at runtime that the file is missing. This feature prevents such issues at compile time.
4. Current workaround is manual: The only way to enforce this today is by manually checking the filesystem or using linting rules, which is not ideal.

Comece revisando como as opções do compilador são definidas e como moduleResolution nodenext resolve imports .js. Determine o comportamento pretendido para arquivos .js ausentes e existentes e, em seguida, adicione cobertura direcionada para a opção proposta. O trabalho estará concluído quando a opção estiver documentada e validada, e seu comportamento estiver coberto por testes.