feat: Option to Ignore window.origin

[lelemm]

I have a use case that I need to run the remote in dev mode but keep attaching it to the host.
This original line
const origin = window ? window.origin : "//${host}:${viteConfig.server?.port}"
prevents me from using the remote this way, because it tries to load the remote from the host url.

Adding this new parameter makes it possible to do this use case and keep the original behavior.

[gioboa]

Thanks @lelemm for your help
Is it similar to #281 ?

[lelemm]

Thanks @lelemm for your help Is it similar to #281 ?

Yes. it's similar. they both achieve the same goal.

[lelemm]

I created a basic example for this:

lelemm/example

npm run dev on both apps (host and remote)

Press the button:

Check your network tab:

It shows the remote with the URL of the host, not the remote as expected

[lelemm]

The way I'm using module-federation is to dynamic load remotes to use as a plugin system for the react host app. This plugin system gets the default of the remote and call it passing some parameter to the plugin initialize.

This change is important to give a nice developer experience when developing plugins to the app (allowing it to hot reload with this PR: vitejs/vite-plugin-react#420 )

[lelemm]

Fixed unit test for this