Is it possible use Dynamic Remote Containers in Vite?

[avrcoelho]

I would like know if is possible use Dynamic Remote Containers in a Vite application?

(async () => {
  // Initializes the shared scope. Fills it with known provided modules from this build and all remotes
  await __webpack_init_sharing__('default');
  const container = window.someContainer; // or get the container somewhere else
  // Initialize the container, it may provide shared modules
  await container.init(__webpack_share_scopes__.default);
  const module = await container.get('./module');
})();

[yuvalkarif]

Hi @avrcoelho,

The main feature of Module Federation v2 is the introduction of the shared runtime. This means all frameworks now utilize the same runtime engine, which can be dynamically configured for various use cases.

The Vite plugin for Module Federation initializes the runtime environment with your desired options, enabling you to statically import them. You can find more details about how it works and how to configure it here.

[zackarychapple]

@underfin @IWANABETHATGUY as the Rolldown implementation progresses is there anything we should do to the plugin and documentation that @yuvalkarif mentioned to make it Rolldown specific?