@module-federation/vite 1.23.6 → 1.23.7

package/README.md

@@ -253,6 +253,8 @@ export default defineConfig({
 
 The host app configuration specifies its name, the filename of its exposed remote entry remoteEntry.js, and importantly, the configuration of the remote application to load.
 Object remotes that omit `type` retain the legacy `"var"` default and emit a warning. Use `type: "module"` for Vite ESM remotes. Use `type: "var"` explicitly only for global-format remotes, such as Webpack/Rspack remotes or a Vite remote's `varFilename` output.
+
+The optional `varFilename` wrapper registers the container on `globalThis[name]` and throws if that name already belongs to another global (e.g. `window`, `self`, `location`), even when its value is `0`, `false`, `""` or `null` (e.g. `length`). Use a distinct name or an ESM remote (`type: "module"`). Loading the wrapper again keeps the existing container.
 You can specify the place the host initialization file is injected with the **hostInitInjectLocation** option, which is described in the example code above.
 The **moduleParseTimeout** option allows you to configure the maximum time to wait for module parsing during the build process.
 The **moduleParseIdleTimeout** option is an alternative that resets the timer on every parsed module. It only fires when there has been no module activity for the configured duration, making it suitable for large codebases where the total build time exceeds the fixed timeout.
@@ -267,6 +269,10 @@ loading stays lazy, including with `loaded-first`. Apps without remotes receive
 SSR host bootstrap. Cold development SSR follows the existing Vite 8+ support gate;
 independent SSR builds are supported on Vite 5–8.
 
+A remote the application registers at runtime with `init()` or `registerRemotes()`
+under a configured remote's name or alias replaces that remote for `loadRemote()`
+calls. Static `import "remote/expose"` statements keep using the configured entry.
+
 Dependencies externalized by Vite keep Node's own runtime resolution. Their runtime
 imports are not bound to the application's instance by this bootstrap.
 Include runtime-consuming dependencies in Vite's `ssr.noExternal` when they need