René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Mark ~module~ `namespace` as deprecated via LS strikethrough","articleBody":"### 🔍 Search Terms\n\nmodule strikethrough namespace internal deprecate\n\n### ✅ Viability Checklist\n\n- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code\n- [X] This wouldn't change the runtime behavior of existing JavaScript code\n- [X] This could be implemented without emitting different JS based on the types of the expressions\n- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)\n- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types\n- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals\n\n### ⭐ Suggestion\n\nSee https://github.com/microsoft/TypeScript/issues/51825#issuecomment-2015163061\n\n### 📃 Motivating Example\n\n```ts\r\nmodule notcool { }\r\n```\n\n### 💻 Use Cases\n\n1. What do you want to use this for? Soft-deprecate internal `module`\r\n2. What shortcomings exist with current approaches? Too breaky\r\n3. What workarounds are you using in the meantime? Being sad\r\n","author":{"url":"https://github.com/RyanCavanaugh","@type":"Person","name":"RyanCavanaugh"},"datePublished":"2024-03-22T20:48:27.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/57913/TypeScript/issues/57913"}