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

首先阅读现有的 compilerOptions 对 paths 的处理，以及 import maps 会影响的 module-resolution 行为。将提议的 importMap 选项与 import-map aliases 和 scopes 进行比较，然后在实现之前定义受支持的配置和兼容性行为；完成的标准是形成一份经过评审的设计，覆盖所述的 Node 和 Deno workspace 使用场景。