Jiannan Zhang

The temporary test case of vite-plugin-federation only supports `esm` and `systemjs`. It is not clear what will happen when using `iife`. I will try it when I have time.

Maybe I can't deal with this problem, because code-spliting is a must for this plugin.

> As a matter of fact, iv׳e also tried with a `rollup` `iife` plugin, just for a small starter app, and even then - i couldn't produce an cjs chunks...

I tried the latest version v1.2.3 and indeed encountered the issue. It works fine when I use localhost, but there are problems when I switch to 127.0.0.1.

Tried it out and it's strange that when not using `server:{host: 127.0.0.1}` to bind the host to 127.0.0.1, accessing 127.0.0.1 directly will be refused.

Dependent on this PR, both 127.0.0.1 and localhost can be used normally after configuring `server:{host:127.0.0.1}`. The latest Release does not yet contain this part of the code, which makes it...

Great, thank you for your contribution. I previously attempted to add the remoteEntry file in dev mode, but failed due to Vite's bundless characteristic.

When I have some free time, I will start the code review.

@jlillywhite @jlillywhite-mc Thanks for your great work, I tried to test with vue3-demo-esm, but I found that it fails, and since there is no modification to the documentation for this...

I added a line to [packages/examples/vue3-demo-esm/package.json](https://github.com/originjs/vite-plugin-federation/blob/main/packages/examples/vue3-demo-esm/package.json#L15) that I can use to test the effect of dev remotes ``` bash dev:remotes": "pnpm --parallel --filter \"./home\" --filter \"./css-modules\" --filter \"./common-lib\" --filter \"./dynamic-remote\"...