Support `@import` JSDoc tag for auto-imports

🔍 Search Terms

"jsdoc @import", "@import auto-import", "jsdoc auto-import"

✅ 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

Since #57207 it is possible to use the JSDoc @import tag.

/** @import { Foo } from 'foo.js'; */

/** @type {Foo} */
const foo = ...;

However, auto-imports still only use the old inline syntax:

/** @type {import('foo.js').Foo} */
const foo = ...;

It would be nice to also have the option to chose the new @import syntax for the auto-imports, either by configuring an option somewhere or simply by adding another action that can be exposed in IDEs.

📃 Motivating Example

I believe this falls in line with the ergonomics goals outlined by the original issue about having a nicer syntax for JSDoc imports #22160.

I will not repeat the arguments made therein, but suffice to say that it produces more readable code.

💻 Use Cases

Having the auto-import work with this syntax would:

• Save time, not having to write import statements by hand.
• Avoid mistakes due to typos, etc.
• Help people adopt the existing feature.

(I have opened the issue here instead of over in vscode. Based on my understanding, this behavior is exposed by the TypeScript Language Server and not by the individual IDEs. Please correct me if I'm wrong.)

Beginne mit der Lektüre des hier beschriebenen Verhaltens des TypeScript Language Server und des Kontexts in den Issues #57207 und #22160. Verfolge, wie auto-imports derzeit Inline-JSDoc-Imports erzeugen, und ermittle anschließend, ob das unterstützte Ergebnis eine Konfigurationsoption oder eine separate Aktion sein sollte; die Aufgabe ist erledigt, wenn auto-imports die angeforderte @import-Syntax erzeugen können.