Loading remoteEntry dynamically from a server for different versions

Hey everyone, First of all, thank you for the amazing work you’ve done with the module federation feature. I have an issue I can’t understand its origin, I have a remote widget that is being consumed in a host, it has multiple versions. For example 0.0.1 and 0.0.2 I load the remoteEntry as follows: http://localhost:8888/api/components/modules/widget-name/0.0.1/remote-entry.js for 0.0.1 and http://localhost:8888/api/components/modules/widget-name/0.0.2/remote-entry.js for version 0.0.2 I’m using the following example: https://github.com/module-federation/module-federation-examples/tree/master/advanced-api/dynamic-remotes when version 0.0.1 initially loads and then I switch to 0.0.2 - the widget that is being loaded is still 0.0.1, if I reload the page then I get version 0.0.2 and vice-versa.

widget federation config: new ModuleFederationPlugin({ name, filename: 'remote-entry.js', exposes :{ './App': './src/App.tsx' }, shared: { ...deps, react: { singleton: true, requiredVersion: deps.react, }, 'react-dom': { singleton: true, requiredVersion: deps['react-dom'], }, }, })

While debugging the following code: function loadComponent(scope, module) { return 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[scope]; // or get the container somewhere else // Initialize the container, it may provide shared modules await container.init(__webpack_share_scopes__.default); const factory = await window[scope].get(module); const Module = factory(); return Module; }; }

I’ve noticed that when trying to load version 0.0.2 (after loading 0.0.1) Module is actually from version 0.0.1.

Update: Just wanted to add that I use react-router for navigation. Another thing I’ve noticed in the Network tab is that for the initial load I can see remote-entry.js file and some more chunks load as well, where when I navigate to the page of version 0.0.2 only the remote-entry.js file is being loaded without the chunks

Can anyone help me understand what is wrong, please?

Thank you very much in advance

[ScriptedAlchemy]

Shouldn’t need to hash module ids. But hashing chunks is a good idea

[DmitryMorlender]

I’ve already tried it without @remoteurl because I want to be flexible with the remote url. The scenario was as follows:

1. Load version 0.0.1 and show it - worked.
2. Load version 0.0.2 and show it - worked. BUT
3. return to version 0.0.1 - loads 0.0.2

I found that making versioned hash moduleIds and chunkIds solves my issue, not sure this is the best way to achieve it though.