🔍 Search Terms

noUncheckedSideEffectImports

✅ 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

Enable noUncheckedSideEffectImports flag by default

📃 Motivating Example

It's useful and could have been missed by many people. It's enabled on Vite starter templates since it was added

💻 Use Cases

• Improve existing TS configurations and catch in IDE bad imports
• Have one less flag to enable when setting up a new project