element-plus in dev mode error, because rollup changes the vue method name about vite-plugin-federation HOT 4 CLOSED

@flyfishzy @ruleeeer

Some other scenarios：
In branch feat-vue-treeshake, home use element-plus, common-lib use vue only. The vue generated by packaging has different exports in these two project.
If layout(host) want use components from these two project, 'Uncaught (in promise) TypeError: createBaseVNode is not a function' will happen.

from vite-plugin-federation.

Idea 1: Prevent rollup from extracting common code.
Idea 2: Restore the Aggregating file generated by rollup

from vite-plugin-federation.

• try idea 1
  We use multiple entry points for code splitting. In this example, the input entry will be:

input: {
    index: '\\vue3-demo\\layout\\index.html',
    __rf_input__vue: 'vue',
    __rf_input__vuex: 'vuex',
    '__rf_input__element-plus': 'element-plus'
  },

The dependency graph is:

index -> element-plus -> vue
index -> vue

Rollup will never duplicate code and instead create additional chunks to only ever load the bare minimum necessary.

The dist bundle of vue will have 2 files, vue.74c5cc83.js is the main logic, while __rf_input__vue.c614e824.js has only imports/exports.

I have tried to set output.hoistTransitiveImports to false, but it makes no difference.

from vite-plugin-federation.

I will try to block the removal of the multi-generated dependency file, use the proxy to proxy the original dependency, and analyze the differences between the two files to add the missing export to the proxy

from vite-plugin-federation.