loading a remote wipes out the registered shared modules by the host even if they are declared singleton about universe HOT 8 OPEN

federation is assign based, it object assigns new over old, since the keys (version) is the same - it doesn't matter to init order.
You can put it into loaded-first which may prevent this.

import type { FederationRuntimePlugin } from '@module-federation/enhanced/runtime';

const sharedStrategy: () => FederationRuntimePlugin = () => ({
  name: 'shared-strategy-plugin',
  beforeInit(args) {
    const { userOptions } = args;
    const shared = userOptions.shared;
    if (shared) {
      Object.keys(shared).forEach((sharedKey) => {
        const sharedConfigs = shared[sharedKey];
        const arraySharedConfigs = Array.isArray(sharedConfigs)
          ? sharedConfigs
          : [sharedConfigs];
        arraySharedConfigs.forEach((s) => {
          s.strategy = 'loaded-first';
        });
      });
    }
    return args;
  },
});
export default sharedStrategy;

from universe.

The solution works! but .....

It works when I use @module-federation/enhanced/webpack. But when I use webpack/lib/container/ModuleFederationPlugin.js, it doesn't work because there's no concept of runtime plugins in that.

I have updated my above mentioned stackblitz example to reflect it.

But interestingly, beforeInit is not even called for the MF 1.0 remote. Even if it is called, because there's no federation runtime, the only way a MF 1.0 remote will not wipe out the share scope is if we forcefully add loaded: true to the packages provided by the host.

Hence my proposal is to modify the SharedBaseArgs to add one additional param to mark any module as loaded. If loaded: true is an internal state, we can rename it to something else like preferred or whatever, but internally it will mark that module as loaded: true after which MF 1.0 container will start using it.

from universe.