Support for Import Maps

🔍 Search Terms

import, map, path, alias, scope

✅ 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'm curious to hear thoughts on introducing an importMap option in compilerOptions.

Some initial thoughts:

• Import maps are a WICG standard.
• They can effectively replace paths for most use cases.
• They're supported by Deno.
• Projects with colocated Node and Deno workspaces could leverage the same source of truth regarding imports/aliases.
• Import maps provide the ability to configure scopes (extremely useful in my experience)

📃 Motivating Example

Every project that utilizes import maps.

💻 Use Cases

1. What do you want to use this for?

Simplifying my configuration in projects that contain both Node and Deno workspaces.

2. What shortcomings exist with current approaches?

One needs to re-specify their aliases in numerous places.

3. What workarounds are you using in the meantime?

N/A

まず、paths に対する既存の compilerOptions の処理と、import maps の影響を受ける module-resolution の動作を読みます。提案された importMap オプションを import-map の aliases および scopes と比較し、実装前にサポート対象の設定と互換性の動作を定義します。完了の条件は、指定された Node および Deno の workspace ユースケースをカバーするレビュー済みの設計があることです。