Load declarations for dynamic imports

[LabEG]

Suggestion

⭐ Suggestion

Now the typescript import declaration files only from node_modules.
I also suggest importing declaration files for dynamic imports.

📃 Motivating Example

In the current version of the typescript, the widget will have the type any.
After the implementation of this feature, the widget must have a type from declarations, check types, and help the developer write code.

const widget = await import("https://some-site/widget-microfront.esnext.min.js");
widget.render(this.microfontElement, {app: {serverUrl: location.origin}});

💻 Use Cases

Development of distributed microfrontends.
This feature will allow you to make much larger distributed applications.

✅ Viability 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. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

[MartinJohns]

This sounds like #24550.

[LabEG]

No. This is another feature.
Proposal #24550 asks to add static imports from external domains.
My suggestion is to import declarations for dynamic imports.

[fatcerberus]

#24550 specifically mentions dynamic import from a domain in the OP and wants the import to be typed, just like this issue.

[MartinJohns]

Then it sounds like #35749.

[typescript-bot]

This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.