@module-federation/vite 1.14.4 → 1.15.0

package/README.md

@@ -79,11 +79,6 @@ export default defineConfig({
   server: {
     origin: "http://localhost:{Your port}"
   },
-  // Do you need to support build targets lower than chrome89?
-  // You can use 'vite-plugin-top-level-await' plugin for that.
-  build: {
-    target: 'chrome89',
-  },
   [...]
 });
 ```
@@ -157,11 +152,6 @@ export default defineConfig({
   server: {
     origin: "http://localhost:{Your port}"
   },
-  // Do you need to support build targets lower than chrome89?
-  // You can use 'vite-plugin-top-level-await' plugin for that.
-  build: {
-    target: 'chrome89',
-  },
   [...]
 });
 ```
@@ -190,15 +180,20 @@ const RemoteMFE = defineAsyncComponent( 👈
 </template>
 ```
 
-## ⚠️ `codeSplitting: false` is not supported
+## ⚠️ `codeSplitting` settings are controlled by the plugin
+
+Do not set either `build.rollupOptions.output.codeSplitting` or
+`build.rolldownOptions.output.codeSplitting` to `false` with this plugin — it will be **automatically ignored**.
 
-Do not set `build.rolldownOptions.output.codeSplitting` to `false` with this plugin — it will be **automatically ignored**.
-Module federation requires chunk splitting to isolate shared dependencies and remote entries into separate chunks.
+`codeSplitting.groups` is also ignored because grouping shared-runtime chunks can break MF init order.
+Module Federation needs `loadShare` and `runtimeInitStatus` isolated into separate chunks for correct bootstrap behavior.
 
 ## ⚠️ `manualChunks` is not supported
 
-Do not use `build.rollupOptions.output.manualChunks` with this plugin — it will be **automatically ignored**.
-Module federation transforms shared dependency imports with top-level `await`, and grouping these transformed modules into a single chunk creates circular async dependencies that cause the application to silently hang.
+Do not use `build.rollupOptions.output.manualChunks` or
+`build.rolldownOptions.output.manualChunks` with this plugin — it will be **automatically ignored**.
+The plugin manages the runtime chunk graph itself, and forcing custom chunk grouping can break Module Federation bootstrap order.
+The plugin injects the splits it needs so `runtimeInitStatus` and `loadShare` stay isolated.
 
 ### So far so good 🎉