Modules Federation 2.0 with local modules (static module federation)

[cclap2020]

Hey guys.

My question is about the possibility of using MFE2.0 to consume local modules/Apps rather than fetching the resources from the URL.

From what I understand (using rsbuild setup).

MFE 2.0 will

1. Fetch the resources based on the config that we provide in the moduleFederation plugin, the config we pass to the initi function from @module-federation/enhanced/runtime, and custom plugins.
2. Consume the resources (lazy load) via loadRemote from @module-federation/enhanced/runtime

I am not super familiar with the actual source code, I checked some, but from what I understand, the first step of fetching and registering the resources, things like mf-manifest.json or remoteEntry.js will require an URL.

Is there a known solution or if you know an idea to consume the local module, a direct dependencies of the host that includes transpiled/compiled code which also includes mf-manifest.json or remoteEntry.js

I looked into custom custom plugin example, it looks like it still only care about the remotes config.

Main reason:

Since the whole point of making the API call is to get the info of compiled/transpiled code (I think). It sounds reasonable to be able to do the same to the local module as it can contain all the necessary files such as mf-manifest.json, and etc.

I would assume with this approach, when we build the host, it should also build with those static apps.

[ScriptedAlchemy]

if its backend or server side it can work, you just pass a relative path as the remote.
For client side apps, it doesnt really make sense. Youd just use npm as the effect will be the same.
Remotes are external modules.