module federation with different environments - MODERNJS

[jonmean]

I have a case where I need to support different environments to consume my federated elements

example:

export default createModuleFederationConfig({
   name: 'host',
   remotes: {
     remote: `remote@http:localhost:3000/static/js/remoteEntry.js`,
   },
   shared: {
      react: { singleton: true },
     'react-dom': { singleton: true },
   },
});

but this http:localhost:3000 can be:

dev.mysite.com
hml.mysite.com
mysite.com

I wouldn't like to create different images for my environments, is there a way to make this remote dynamic according to the environment? if it is dev, consume remote from the dev link, if it is hml from hml and so on?

using process.env does not work

[ScriptedAlchemy]

use a runtime plugin and rewrite the configs at runtime in init or beforeRequest - you can also check the runtime-plugins folder in federation examples