Support source phase imports

🔍 Search Terms

import source wasm

✅ 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

Support for source phase imports: https://github.com/tc39/proposal-source-phase-imports

• https://github.com/nodejs/node/pull/56919
• https://github.com/denoland/deno_core/pull/1081

📃 Motivating Example

// wasmModule is WebAssembly.Module
import source wasmModule from "./math.wasm"

💻 Use Cases

1. Getting a wasm module instead of instance.

Lies zunächst den TC39-Vorschlag zu source phase imports sowie die verlinkten Node.js- und Deno-PRs. Verwende das motivierende TypeScript-Beispiel, um den erwarteten Typ des importierten WebAssembly-Moduls und die unterstützte Syntax festzulegen. Die Aufgabe ist abgeschlossen, wenn TypeScript source phase imports akzeptiert und korrekt prüft, ohne das Verhalten des ausgegebenen JavaScript zu ändern.