module federation load it's chunks from a wrong url

[joebnb]

Bug report

What is the current behavior?

remote app

when using module federation webpack will generate:

• entry eg:static/remoteEntry.js
• entry's dependenceies eg:static/remoteEntry_index.ad3ds.js

this remote app this app running in localhost:10000

 new ModuleFederationPlugin({
      name: 'remoteEntry',
      library: { type: 'window', name: 'remoteEntry' },
      filename: 'static/remoteEntry.js',
      exposes: {
        './entry': './src/remoteEntry',
      },
    }),

host app

configurate remoteEntry.js address eg:http://localhost:10000/static/remoteEntry.js in host app.

config like:

  new ModuleFederationPlugin({
      name: 'host',
      remotes: {
        remoteEntry:'portalRemote@http://localhost:10000/static/remoteEntry.js'
      },
    }),

visit host app http://localhost:10001 NOTIC:remote and host are different origin

chrome console will print remoteEntry's chunks will 404 beacause it's will load from http://localhost:10001/remoteEntry_index.ad3ds.js
request were use incorrect origin and lost pathname

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

actually expect if i config host app like http://localhost:10000/static/remoteEntry.js,module federation plugin will load it's dependence from http://localhost:10000/static/ not http://localhost:10001,

if specified remote url, the remote artifacts should read from remote, host app may not have remote app files.

if this is not a bug, would give me some suggestion or explain how to workaround this

---

screenshots

[alexander-akait]

Please provide reproducible test repo using github, I will show how to fix it

[joebnb]

i solved it by using publicpath auto