@module-federation/vite 1.18.1 → 1.19.0

package/README.md

@@ -31,6 +31,7 @@ Examples live in [`gioboa/module-federation-vite-examples`](https://github.com/g
 | ---------------------------------------------------------------------------------------- | --------------- | ----------------- | --------------------------- |
 | [Alpine](https://github.com/gioboa/module-federation-vite-examples/tree/main/alpine)     | `alpine-host`   | `alpine-remote`   | Alpine.js                   |
 | [Angular](https://github.com/gioboa/module-federation-vite-examples/tree/main/angular)   | `angular-host`  | `angular-remote`  | Angular                     |
+| [Astro](https://github.com/gioboa/module-federation-vite-examples/tree/main/astro)       | `astro-host`    | `astro-remote`    | Astro 7                     |
 | [Ember](https://github.com/gioboa/module-federation-vite-examples/tree/main/ember)       | `ember-host`    | `ember-remote`    | Ember 7                     |
 | [Lit](https://github.com/gioboa/module-federation-vite-examples/tree/main/lit)           | `lit-host`      | `lit-remote`      | Lit                         |
 | [Nuxt](https://github.com/gioboa/module-federation-vite-examples/tree/main/nuxt)         | `nuxt-host`     | `nuxt-remote`     | Nuxt 4                      |
@@ -220,6 +221,28 @@ You can specify the place the host initialization file is injected with the **ho
 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.
 
+## Runtime capability optimization
+
+Runtime features that a build never uses can be removed at build time:
+
+```ts
+federation({
+  name: "remote",
+  exposes: {
+    "./remote-app": "./src/App.vue",
+  },
+  disableRemote: true,
+  disableShared: true,
+  disableSnapshot: true,
+});
+```
+
+- `disableRemote` removes remote-consumption support. Do not enable it when `remotes` are configured.
+- `disableShared` removes shared-dependency support. Do not enable it when `shared` dependencies are configured.
+- `disableSnapshot` removes snapshot support, including manifest-based remotes, preload, dynamic type hints, HMR, and devtools integration.
+
+All three options default to `false`, except `disableSnapshot`, which defaults to `true` for Node/SSR builds. An explicitly configured Vite `define` value takes precedence over the corresponding option.
+
 ## Load the Remote App
 
 In your host app, you can now import and use the remote app with **defineAsyncComponent**

package/lib/index.d.ts

@@ -96,6 +96,27 @@ type ModuleFederationOptions = {
    * @default 'web' (or 'node' if build.ssr is enabled)
    */
   target?: 'web' | 'node';
+  /**
+   * Removes remote-consumption support from the federation runtime.
+   * Only enable this for builds that never load remotes.
+   *
+   * @default false
+   */
+  disableRemote?: boolean;
+  /**
+   * Removes shared-dependency support from the federation runtime.
+   * Only enable this when the build has no shared dependencies.
+   *
+   * @default false
+   */
+  disableShared?: boolean;
+  /**
+   * Removes snapshot support, including manifest-based remotes, preload,
+   * dynamic type hints, HMR, and devtools integration.
+   *
+   * @default false (true for Node/SSR builds)
+   */
+  disableSnapshot?: boolean;
   /**
    * Additional packages to mark as external in the SSR remote entry build.
    * Shared packages and MF runtime packages are always external. Use this to