Jiannan Zhang

> Thank u for this package) Do u need some details? If you can provide a simple example, that would be great, but if not, that's fine, I probably know...

> Sry, but there is no time yet, so I won’t be able to drop the repo in the near future It's okay. I can reproduce the problem myself.

@Timehello Thank you for your contribution to this bug,but there seems to be some problems in some other scenarios, it looks like the problem is easy to fix,if you have...

@Timehello I'll try to reproduce it on my machine later, sorry, maybe it's a problem with the environment

Sorry, there are no configuration items that can modify this part yet, but why do you need to change their names?

May provide functions or expressions to profile names, temporarily added to the 2022 H1 program

There is no group about this yet, but you can use the [discussion](https://github.com/originjs/vite-plugin-federation/discussions)

如果使用的是ESM格式的话，会使用`top-level await`特性，必须设置`target:'esnext'` ``` js export default defineConfig({ build: { target: 'esnext', } }) ```

dev模式有一些限制条件，只有完全的host端（不能包含任何expose）才可以使用dev模式，这是因为vite在dev模式下不允许添加chunk，自然也无法生成remoteEntry

如果使用的框架是react,我不建议使用dev模式，因为react的打包格式一直是cjs，调整dev（esbuild）和build（rollup）打包cjs库行为一致不是一件容易的事情，当然如果react升级为ESM的库，这个问题就不存在了