Missing ts(2307) on side effect imports

[MaciejZoopit]

🔍 Search Terms

compiler option to prevent importing non-existent files

✅ 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

I would like to see an error when importing a module, that doesn't exist

📃 Motivating Example

I have util repo, where I recently added a module called new-module
In other repos I wanted to import it, I did it like that:
import '@company/util/cjs/new-module'

And the problem is that TS doesn't care if this module exists. I get no error even when I do this:
import 'asdasd'

Before I deployed my changes I should have updated util to the newer version with new-module, but I forgot. I wish TS informed me that this module doesn't exist for this version of util and prevented me from building the code.

My suggestion is to add a check to this:
import '@company/util/cjs/new-module'

💻 Use Cases

1. Validate imports of modules
2. Modules are not validated
3. My current workaround is:

import {} from '@company/util/cjs/new-module'
import '@company/util/cjs/new-module'

One line checks if I have the module and the other imports it. Not very neat though

[fatcerberus]

Duplicate of #50394.

[typescript-bot]

This issue has been marked as "Duplicate" and has seen no recent activity. It has been automatically closed for house-keeping purposes.