[Bug]: When the base attribute is set from the vite define Config, is not reflecting in mf-manifest.json

[siddiq-rehman]

Describe the bug

Hello,

When are dynamically registering a MFE with "registerRemotes" in the host using the mf-manifest file, let us say,

registerRemotes([
{
name: 'testMFE', // This is hello world mfe
entry: 'http://localhost:6001/mf-manifest.json',
type: 'manifest',
}
])

Now when it tries to load the remoteEntry from testMFE, it is pointing to the host server path. I instead of setting publicPath, I did set vite base path, But it is not reflecting in the mf-manifest.json.

So, when I set the publicPath in the mfe to "http://localhost:6001", It is all fine, But now I cannot run the MFE in dev mode due to

 dcpNextGenMfe__H_A_I…oInit__H_A_I__.js:3 
 Uncaught TypeError: Failed to resolve module specifier 'http://localhost:6001http://localhost:6001/remoteEntry-[hash]'
    at testMfe__H_A_I…it__H_A_I__.js:3:51

Version

7.2.2

Reproduction

NA

Relevant log output

Validations

• Read the docs.
• Read the common issues list.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[gioboa]

Hi @siddiq-rehman, I see, do you have a basic example in a public repository to reproduce this issue?

[github-actions]

As there's been no activity for 30 days, this issue has been flagged as stale. If you'd like it to remain open, please add a comment within the next 7 days. Thank you.