Open in StackBlitz

npm i https://pkg.pr.new/@module-federation/vite@834

commit: 2690494

Yes, of course!

I can confirm that file names are looking better now, remoteEntry's name is remoteEntry.js and I see it also present for the shared modules. The only issue now is with what the MF exposes, there are no linked files for the exposed paths. All the arrays are empty there

The only issue now is with what the MF exposes, there are no linked files for the exposed paths. All the arrays are empty there

I pushed the fix, try this new release please.
npm i https://pkg.pr.new/@module-federation/vite@2690494

Sorry for the delay, I was investigating and testing until now and will share my observations:

• Now I see remoteEntry.js included everywhere
• Since you mentioned yesterday that publicPath '/' resolves to 'auto' internally, I removed it from the configuration. However, this seems to not work for me, not sure if it's specifically for my case or not. For example when I try to access the remote app from the host, it tries to look for https://$hostURL/remoteEntry.js instead of https://$remoteURL/remoteEntry.js . Adding "publicPath": "auto" explicitly fixes it. It is a big ecosystem and I don't have access to the host app to check its configuration. However, I think I might change that if needed further investigation.
• I managed to connect to the remote only by explicitly adding filename: "remoteEntry.js". Otherwise, for me it looks like it fallbacks to some code when file name is not specified, which names the entry point "remoteEntry-hash.js". At least this is what I saw in @id folder in the source files.
• After successfully connecting to the remote on dev, I am able to load the remote files, but getting "$RefreshSig$ is not defined" error. Also not sure if it's related to the package or the project.
• Preview mode still works fine

I see, thanks for you check. I'll merge this PR and let's continue the discussion on the other points.

Thank you too!