TypeScript plugin support

[einarq]

Does the importRemote util work with the MF typescript plugin?

Meaning, if you import a React component like this, does it also preserve any types?

importRemote({ url: "http://localhost:3001", scope: 'Foo', module: 'Bar' }).then(({/* list of Bar exports */}) => {

[einarq]

Btw, I came here via this issue:
module-federation/module-federation-examples#681 (comment)

We are trying to find the best way to actually postpone loading the remoteEntry, and other modules that it drags with it, until any module from this remote is actually needed.
Currently MF has the unfortunate side-effect of pre-loading too much stuff it seems.

[einarq]

Also have this issue over on the external-remotes-plugin:
module-federation/external-remotes-plugin#6

That plugin is deprecated, right? Is "importRemote" the current recommendation?
Or is the recommendation still to use the "promise new Promise" approach mentioned in the docs?

[alex-vukov]

Hi @einarq! I am just seeing this issue. Sorry for the delay. importRemote does not preserve the types from the module it imports dynamically, however it can be passed a generic type which then will be assigned to the resolved object. So you can use it like this for example importRemote<{title: string; children?:JSX.Element;}>({ url: "http://localhost:3001", scope: 'Foo', module: 'Bar' })

[giavinh79]

Would using importRemote to lazy load other remote app remoteEntry.js files have any implications regarding sharing dependencies? As I understand, remoteEntry.js files are by default loaded up front to negotiate shared scope.

EDIT: Based on these docs, seems like it could be fine: https://module-federation.io/guide/basic/runtime.html#differences-between-build-plugins-and-runtime