[Bug]: Cannot share dependencies for mf consumer package

[yf-yang]

Version

System:
    OS: macOS 13.2.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 967.52 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Browsers:
    Chrome: 133.0.6943.98
    Safari: 16.3
  npmPackages:
    @rslib/core: * => 0.5.0

Details

I'm experimenting with rslib to achieve that:

1. Create a lib package as module federation consumer
2. Import the package to another app

Therefore, based on the official rslib example, I created the following structure:

• A package, dep, contains a timestamp when the package is initially loaded
• mf-remote, a mf provider that depends on dep
• mf-react-component, a mf consumer. It loads mf-remote dynamically and it also imports from dep. I expect dep to be shared, which means it should only load once and timestamp should be the same. I also expect mf-react-component could be built as a lib.
• mf-host, an app that imports from mf-react-component

Now I am not sure how to configure rslib.config.ts, I tried the following:

export default defineConfig({
  lib: [
    {
      format: "esm",
      // ...
    },
    {
      format: "cjs",
      // ...
    },
  ],
  // ...
  plugins: [
    pluginModuleFederation({
      name: "rslib_provider",
      exposes: {
        ".": "./src/index.tsx",
      },
      shared: {
        react: {
          singleton: true,
        },
        "react-dom": {
          singleton: true,
        },
        dep: {
          singleton: true,
        },
      },
    }),
  ],
});

However, it seems the output still imports/requires from dep instead of special module federation treatment.

My question is:

1. Should the scenario (build a MF consumer as a lib) be supported?
2. If so, is it currently supported? How to adjust the configuration?

Reproduce link

https://github.com/yf-yang/rslib-experiments

Reproduce Steps

pnpm i
pnpm build:lib
pnpm dev:all:host

Check logs

timestamp from host and timestamp from remote are different

[yf-yang]

Update: I am able to make them shared using runtime mf as a workaround

import * as dep from 'dep'
init({
  shared: {
    dep: {
      lib: () => dep,
      version: '1.0.0',
      shareConfig: {
        singleton: true,
        requiredVersion: '1.0.0',
      }
    }
  }
});

[Timeless0911]

I think singleton of dep should also be configured in mf-host

[yf-yang]

Indeed that could work (that's mf applying to host, not the lib actually).
As a lib, could mf-host import it without event knowing that it is a mf consumer?

[2heal1]

Update: I am able to make them shared using runtime mf as a workaround

import * as dep from 'dep'
init({
shared: {
dep: {
lib: () => dep,
version: '1.0.0',
shareConfig: {
singleton: true,
requiredVersion: '1.0.0',
}
}
}
});

This is correct . Because you use mf runtime to load mf-remote , but you forget pass shared in runtime , so the mf-remote only use itself runtime

[Timeless0911]

Why do you configure the mf plugin in esm format and use the output of esm instead of mf?

[yf-yang]

Why do you configure the mf plugin in esm format and use the output of esm instead of mf?

I want to create a standalone utility package as mf consumer, then import the package to arbitrary apps.
If I got it right, dist/mf/index.js could not be imported, could it?

[yf-yang]

Because you use mf runtime to load mf-remote , but you forget pass shared in runtime , so the mf-remote only use itself runtime

If I configure build time MF plugin shared parameters, then they should be shared correctly? The issue is that the build time plugin is not applied (I don't know if it is an unsupported feature)

[Timeless0911]

MF plugin can only and should configured in mf format.

[yf-yang]

OK ☹ , thank you