Tree Shaking on @module-federation/runtime doesn't work

[nicotu01]

Describe the bug

Module Federation Runtime significantly increases the size of the deliverable.

1. I created a vanilla vite project using the command npm create vite. Then, I deleted all the JavaScript code.

Here is the result of build command :

dist/assets/index-B5Qt9EMX.js  0.71 kB

2. Then, I installed @module/federation-runtime and simply invoked init function from main.ts :

import { init } from "@module-federation/runtime";
init({
  name: "vite-vanilla",
  remotes: [
    { name: "remote1", entry: "http://localhost:4321/assets/remotesEntry.js" },
  ],
});

The result of the build command significantly increases :

dist/assets/index-DjYITZnQ.js  63.77 kB 

When I check the contents of the deliverable, I notice that the entire runtime library is present

Reproduction

https://github.com/nicotu01/vite-vanilla-federation-tree-shaking

Used Package Manager

npm

System Info

-

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.
• Make sure this is a Module federation issue and not a framework-specific issue.
• The provided reproduction is a minimal reproducible example of the bug.

[ScriptedAlchemy]

init requires the full system, runtime cannot be shaken in vite. in webpack and rspack we can share it, making the remotes only 14kb

[nicotu01]

Hi @ScriptedAlchemy !
Without talking about sharing, I'm simply building an application that invokes the init function of @module-federation/runtime

I try it with webpack and have the same result : the bundle size is very heavy.

I just have an ìndex.js :

import { init } from "@module-federation/runtime";
init({
  name: "vite-vanilla",
  remotes: [
    { name: "remote1", entry: "http://localhost:4321/assets/remotesEntry.js" },
  ],
});

And the webpack build result :

dist/assets/index-DjYITZnQ.js  65.93 kB