### 🔍 Search Terms module strikethrough namespace internal deprecate ### ✅ Viability Checklist - [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code - [X] This wouldn't change the runtime behavior of existing JavaScript code - [X] This could be implemented without emitting different JS based on the types of the expressions - [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.) - [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types - [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals ### ⭐ Suggestion See https://github.com/microsoft/TypeScript/issues/51825#issuecomment-2015163061 ### 📃 Motivating Example ```ts module notcool { } ``` ### 💻 Use Cases 1. What do you want to use this for? Soft-deprecate internal `module` 2. What shortcomings exist with current approaches? Too breaky 3. What workarounds are you using in the meantime? Being sad
🔍 Search Terms
module strikethrough namespace internal deprecate
✅ Viability Checklist
⭐ Suggestion
See #51825 (comment)
📃 Motivating Example
💻 Use Cases
module