A DRY-er syntax for jsdoc types imports

[nojvek]

Suggestion

So the current way of importing things in JS land for types declared in .d.ts is kind of really redundant

/** @typedef { import('./my-types').Foo } Foo */
/** @typedef { import('./my-types').Bar } Bar */
/** @typedef { import('./my-types').Hello } Hello */
/** @typedef { import('./my-types').World } World */

This violates the DRY principle and kind of looks awful.

Can we have a similar import syntax to the .ts and normal .js versions ?

/** @import {Foo, Bar, Hello, World} from './my-types' **/

Checklist

My suggestion meets these guidelines:

• 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. new expression-level syntax)

[DanielRosenwasser]

Duplicate of #22160?

[nojvek]

Yeah but the other issue is closed right?

I’ve started campaigning for typed js at my current workplace however the redundant type import syntax makes everyone 🤮 at my PRs

[ghost]

The other issue is open.

[nojvek]

@weswigham is this actually fixed now? I’m not sure why it’s being closed without a reason.

[weswigham]

Because it does sufficiently duplicate #22160 which is actually open.