@bleedingdev/modern-js-app-tools 3.5.0-ultramodern.100 → 3.5.0-ultramodern.102

package/docs/configure/app/output/{source-map.mdx → source-map.md}

@@ -1,7 +1,3 @@
----
-title: sourceMap
----
-
 # output.sourceMap
 
 - **Type:**
@@ -29,6 +25,6 @@ When `output.sourceMap` is not configured, the source map generation rules of Mo
 - In the development mode, JS and CSS source maps are generated for development debugging.
 - In the production mode, JS source maps are generated for stack trace backtracking, and CSS source maps are not generated to provide the best build performance.
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="output.sourceMap" />
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - output.sourceMap](https://v2.rsbuild.dev/config/output/source-map).
+:::

package/docs/configure/app/output/{split-route-chunks.mdx → split-route-chunks.md}

@@ -1,7 +1,3 @@
----
-title: splitRouteChunks
----
-
 # output.splitRouteChunks
 
 - **Type:** `boolean`

package/docs/configure/app/output/{ssg.mdx → ssg.md}

@@ -1,7 +1,3 @@
----
-title: ssg
----
-
 # output.ssg
 
 - **Type:** `boolean | object`
@@ -10,16 +6,17 @@ title: ssg
 Configuration to enable the application’s SSG (Static Site Generation) feature.
 
 :::tip Enabling SSG
-This configuration takes effect only when SSG is enabled. Please read the [Static Site Generation](/guides/basic-features/render/ssg) documentation to understand how to enable SSG and its use cases.
+This configuration takes effect only when SSG is enabled. Please read the [Static Site Generation](/guides/basic-features/render/ssg.md) documentation to understand how to enable SSG and its use cases.
 
 :::
 
 :::info Recommended Reading
-The SSG feature is closely related to routing. It is recommended to understand the [routing solution](/guides/basic-features/routes/routes) before using SSG.
+The SSG feature is closely related to routing. It is recommended to understand the [routing solution](/guides/basic-features/routes/routes.md) before using SSG.
 
 :::
 
 :::info
+
 - Use `output.ssg` for single-entry apps.
 - For multi-entry apps, prefer `output.ssgByEntries`.
 - If `output.ssg` is `true` and `output.ssgByEntries` is not set, all routes under all entries are treated as SSG routes.
@@ -82,4 +79,3 @@ export default defineConfig({
   },
 });
 ```
-

package/docs/configure/app/output/{ssgByEntries.mdx → ssgByEntries.md}

@@ -1,7 +1,3 @@
----
-title: ssgByEntries
----
-
 # output.ssgByEntries
 
 - **Type:** `Record<string, boolean | object>`
@@ -10,6 +6,7 @@ title: ssgByEntries
 Configure SSG per entry for multi-entry applications.
 
 :::info
+
 - Use `output.ssg` for single-entry apps.
 - For multi-entry apps, prefer `output.ssgByEntries`.
 - If `output.ssg` is `true` and `output.ssgByEntries` is not set, all routes under all entries are treated as SSG routes.

package/docs/configure/app/output/{svg-default-export.mdx → svg-default-export.md}

@@ -1,7 +1,3 @@
----
-title: svgDefaultExport
----
-
 # output.svgDefaultExport
 
 - **Type:** `'url' | 'component'`

package/docs/configure/app/output/{temp-dir.mdx → temp-dir.md}

@@ -1,7 +1,3 @@
----
-title: tempDir
----
-
 # output.tempDir
 
 - **Type:** `string`

package/docs/configure/app/performance/{build-cache.mdx → build-cache.md}

@@ -1,7 +1,3 @@
----
-title: buildCache
----
-
 # performance.buildCache
 
 - **Type:**
@@ -43,6 +39,6 @@ export default {
 };
 ```
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="performance.buildCache" />
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - performance.buildCache](https://v2.rsbuild.dev/config/performance/build-cache).
+:::

package/docs/configure/app/performance/{chunk-split.mdx → chunk-split.md}

@@ -1,7 +1,3 @@
----
-title: chunkSplit
----
-
 # performance.chunkSplit
 
 - **Type:** `Object`
@@ -39,6 +35,6 @@ interface SplitCustom {
 export type ChunkSplit = BaseChunkSplit | SplitBySize | SplitCustom;
 ```
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="performance.chunkSplit" />
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - performance.chunkSplit](https://v2.rsbuild.dev/config/performance/chunk-split).
+:::

package/docs/configure/app/performance/{dns-prefetch.mdx → dns-prefetch.md}

@@ -1,7 +1,3 @@
----
-title: dnsPrefetch
----
-
 # performance.dnsPrefetch
 
 - **Type:** `undefined | string[]`
@@ -14,6 +10,6 @@ After this property is set, the domain name can be resolved before the resource
 
 See [Using dns-prefetch](https://developer.mozilla.org/en-US/docs/Web/Performance/dns-prefetch) for more details.
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="performance.dnsPrefetch" />
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - performance.dnsPrefetch](https://v2.rsbuild.dev/config/performance/dns-prefetch).
+:::

package/docs/configure/app/performance/preconnect.md

@@ -0,0 +1,16 @@
+# performance.preconnect
+
+- **Type:** `undefined | Array<string | PreconnectOption>`
+
+```ts
+interface PreconnectOption {
+  href: string;
+  crossorigin?: boolean;
+}
+```
+
+- **Default:** `undefined`
+
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - performance.preconnect](https://v2.rsbuild.dev/config/performance/preconnect).
+:::

package/docs/configure/app/performance/{prefetch.mdx → prefetch.md}

@@ -1,7 +1,3 @@
----
-title: prefetch
----
-
 # performance.prefetch
 
 - **Type:** `undefined | true | PrefetchOption`
@@ -20,6 +16,6 @@ interface PrefetchOption {
 
 - **Default:** `undefined`
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="performance.prefetch" />
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - performance.prefetch](https://v2.rsbuild.dev/config/performance/prefetch).
+:::

package/docs/configure/app/performance/{preload.mdx → preload.md}

@@ -1,7 +1,3 @@
----
-title: preload
----
-
 # performance.preload
 
 - **Type：** `undefined | true | PreloadOption`
@@ -22,6 +18,6 @@ interface PreloadOption {
 
 Inject the [`<link rel="preload">`](https://developer.mozilla.org/zh-CN/docs/Web/HTML/Attributes/rel/preload) tags for the static assets generated by Rsbuild.
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="performance.preload" />
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - performance.preload](https://v2.rsbuild.dev/config/performance/preload).
+:::

package/docs/configure/app/performance/{print-file-size.mdx → print-file-size.md}

@@ -1,7 +1,3 @@
----
-title: printFileSize
----
-
 # performance.printFileSize
 
 - **Type:**
@@ -39,6 +35,6 @@ info    Production file sizes:
   dist/static/css/main.03221f72.css         1.4 kB       741 B
 ```
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="performance.printFileSize" />
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - performance.printFileSize](https://v2.rsbuild.dev/config/performance/print-file-size).
+:::

package/docs/configure/app/performance/profile.md

@@ -0,0 +1,10 @@
+# performance.profile
+
+- **Type:** `boolean`
+- **Default:** `false`
+
+Whether capture timing information for each module, same as the [profile](https://rspack.rs/config/other-options#profile) config of Rspack.
+
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - performance.profile](https://v2.rsbuild.dev/config/performance/profile).
+:::

package/docs/configure/app/performance/remove-console.md

@@ -0,0 +1,10 @@
+# performance.removeConsole
+
+- **Type:** `boolean | ConsoleType[]`
+- **Default:** `false`
+
+Whether to remove `console.[methodName]` in production build.
+
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - performance.removeConsole](https://v2.rsbuild.dev/config/performance/remove-console).
+:::

package/docs/configure/app/performance/remove-moment-locale.md

@@ -0,0 +1,10 @@
+# performance.removeMomentLocale
+
+- **Type:** `boolean`
+- **Default:** `false`
+
+Whether to remove the locales of [moment.js](https://momentjs.com/).
+
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - performance.removeMomentLocale](https://v2.rsbuild.dev/config/performance/remove-moment-locale).
+:::

package/docs/configure/app/performance/{rsdoctor.mdx → rsdoctor.md}

@@ -1,7 +1,3 @@
----
-title: rsdoctor
----
-
 # performance.rsdoctor
 
 - **Type:**

package/docs/configure/app/{plugins.mdx → plugins.md}

@@ -3,15 +3,15 @@
 - **Type:** `CliPlugin[]`
 - **Default:** `[]`
 
-Used to configure custom Modern.js framework CLI plugins. For information on how to create custom CLI plugins, please refer to [How to Write CLI Plugins](/plugin/introduction.html#cli-plugins).
+Used to configure custom Modern.js framework CLI plugins. For information on how to create custom CLI plugins, please refer to [How to Write CLI Plugins](/plugin/introduction.md#cli-plugins).
 
 ## Note
 
 This option is **specifically for configuring framework CLI plugins**. If you need to configure other types of plugins, use the appropriate configuration method:
 
-- Use [builderPlugins](/configure/app/builder-plugins) for Rsbuild plugins.
-- Use [tools.bundlerChain](/configure/app/tools/bundler-chain) for Rspack plugins.
-- Use the [plugins field in runtime config](/configure/app/runtime/plugins) for framework Runtime plugins.
+- Use [builderPlugins](/configure/app/builder-plugins.md) for Rsbuild plugins.
+- Use [tools.bundlerChain](/configure/app/tools/bundler-chain.md) for Rspack plugins.
+- Use the [plugins field in runtime config](/configure/app/runtime/plugins.md) for framework Runtime plugins.
 
 ## Examples
 

package/docs/configure/app/resolve/{alias-strategy.mdx → alias-strategy.md}

@@ -1,7 +1,3 @@
----
-title: aliasStrategy
----
-
 # resolve.aliasStrategy
 
 - **Type:** `'prefer-tsconfig' | 'prefer-alias'`
@@ -9,6 +5,6 @@ title: aliasStrategy
 
 Set the strategy for path alias resolution, to control the priority relationship between the paths option in `tsconfig.json` and the [resolve.alias](https://v2.rsbuild.rs/config/resolve/alias) option of Rsbuild.
 
-import RsbuildConfig from '@site-docs/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="resolve.aliasStrategy" />
+:::info
+该配置项的使用方式与 Rsbuild 完全一致。详细信息请参考 [Rsbuild - resolve.aliasStrategy](https://v2.rsbuild.dev/config/resolve/alias-strategy)。
+:::

package/docs/configure/app/resolve/alias.md

@@ -0,0 +1,9 @@
+# resolve.alias
+
+- **Type:** `string[]`
+
+Create aliases for module paths to simplify import paths or redirect module references.
+
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - resolve.alias](https://v2.rsbuild.dev/config/resolve/alias).
+:::

package/docs/configure/app/resolve/{condition-names.mdx → condition-names.md}

@@ -1,7 +1,3 @@
----
-title: conditionNames
----
-
 # resolve.conditionNames
 
 - **Type:** `string[]`
@@ -9,10 +5,9 @@ title: conditionNames
 
 Specifies the condition names used to match entry points in the [exports](https://nodejs.org/api/packages.html#packages_exports) of a package.
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="resolve.extensions" />
-
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - resolve.extensions](https://v2.rsbuild.dev/config/resolve/extensions).
+:::
 :::warning
 Do not enable this configuration option for SSR applications, as it will cause SSR rendering to fail.
 :::

package/docs/configure/app/resolve/{dedupe.mdx → dedupe.md}

@@ -1,13 +1,9 @@
----
-title: dedupe
----
-
 # resolve.dedupe
 
 - **Type:** `string[]`
 
 Force Rsbuild to resolve the specified packages from project root, which is useful for deduplicating packages and reducing the bundle size. same as the [resolve.dedupe](https://v2.rsbuild.rs/config/resolve/dedupe) config of Rsbuild.
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="resolve.dedupe" />
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - resolve.dedupe](https://v2.rsbuild.dev/config/resolve/dedupe).
+:::

package/docs/configure/app/resolve/{extensions.mdx → extensions.md}

@@ -1,7 +1,3 @@
----
-title: extensions
----
-
 # resolve.extensions
 
 - **Type:** `string[]`
@@ -9,10 +5,9 @@ title: extensions
 
 Automatically resolve file extensions when importing modules. This means you can import files without explicitly writing their extensions.
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="resolve.extensions" />
-
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - resolve.extensions](https://v2.rsbuild.dev/config/resolve/extensions).
+:::
 :::warning
 Do not enable this configuration option for SSR applications, as it will cause SSR rendering to fail.
 :::

package/docs/configure/app/runtime/{0-intro.mdx → 0-intro.md}

@@ -52,10 +52,7 @@ export default defineRuntimeConfig(entryName => {
 
 :::tip
 
-Using the `src/modern.runtime.ts` configuration approach does not support exporting asynchronous functions, which is related to the rendering method of Modern.js. If you need to add asynchronous logic, please use the **[Runtime Plugin](/plugin/introduction.html#runtime-plugin)**.
+Using the `src/modern.runtime.ts` configuration approach does not support exporting asynchronous functions, which is related to the rendering method of Modern.js. If you need to add asynchronous logic, please use the **[Runtime Plugin](/plugin/introduction.md#runtime-plugin)**.
 
 :::
 
-import RuntimeCliConfig from '@site-docs/components/runtime-cli-config';
-
-<RuntimeCliConfig />

package/docs/configure/app/runtime/{plugins.mdx → plugins.md}

@@ -3,7 +3,7 @@
 - **Type:** `RuntimePlugin[]`
 - **Default:** `[]`
 
-Used to configure custom Modern.js Runtime plugins. For details on how to create custom Runtime plugins, please refer to [How to Write Runtime Plugins](/plugin/introduction#runtime-plugins).
+Used to configure custom Modern.js Runtime plugins. For details on how to create custom Runtime plugins, please refer to [How to Write Runtime Plugins](/plugin/introduction.md#runtime-plugins).
 
 :::info
 

package/docs/configure/app/runtime/{router.mdx → router.md}

@@ -1,18 +1,14 @@
----
-title: router
----
-
 # router
 
 - **Type:** `Object`
 - **Default:** `{}`
 
-This configuration item is used to configure client-side routing, supporting the use of [conventional routing](/guides/concept/entries.html#convention-routing) provided by Modern.js for routing management.
+This configuration item is used to configure client-side routing, supporting the use of [conventional routing](/guides/concept/entries.md#convention-routing) provided by Modern.js for routing management.
 
 :::note
 The `router` configuration item **only takes effect when using conventional routing entries** (i.e., when there is a `routes/` directory in the entry). For controlled routing entries or custom entries, this configuration will not take effect.
 
-In multi-entry applications, you can configure different routing behaviors for different entries using the function form of `defineRuntimeConfig`. For more details, see [Runtime Configuration Introduction](/configure/app/runtime/0-intro#multi-entry-configuration).
+In multi-entry applications, you can configure different routing behaviors for different entries using the function form of `defineRuntimeConfig`. For more details, see [Runtime Configuration Introduction](/configure/app/runtime/0-intro.md#multi-entry-configuration).
 :::
 
 ## basename
@@ -23,7 +19,7 @@ In multi-entry applications, you can configure different routing behaviors for d
 Sets the `basename` for client-side routing, typically used when the application needs to be deployed under a non-root path of the domain.
 
 :::tip
-It is recommended to use [`server.baseUrl`](/configure/app/server/base-url) for configuration.
+It is recommended to use [`server.baseUrl`](/configure/app/server/base-url.md) for configuration.
 :::
 
 ## supportHtml5History

package/docs/configure/app/security/{check-syntax.mdx → check-syntax.md}

@@ -1,7 +1,3 @@
----
-title: checkSyntax
----
-
 # security.checkSyntax
 
 - **Type:**

package/docs/configure/app/security/{nonce.mdx → nonce.md}

@@ -1,7 +1,3 @@
----
-title: nonce
----
-
 # security.nonce
 
 - **Type:**
@@ -14,6 +10,6 @@ type Nonce = string;
 
 Adding a `nonce` attribute to the scripts resources introduced for HTML. This allows the browser to determine whether the script can be executed when it parses inline scripts with matching nonce values.
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="security.nonce" />
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - security.nonce](https://v2.rsbuild.dev/config/security/nonce).
+:::

package/docs/configure/app/security/{sri.mdx → sri.md}

@@ -1,7 +1,3 @@
----
-title: sri
----
-
 # security.sri
 
 - **Type**

package/docs/configure/app/server/{base-url.mdx → base-url.md}

@@ -1,7 +1,3 @@
----
-title: baseUrl
----
-
 # server.baseUrl
 
 - **Type:** `string | string[]`

package/docs/configure/app/server/{port.mdx → port.md}

@@ -1,7 +1,3 @@
----
-title: port
----
-
 # server.port
 
 - **Type:** `number`
@@ -17,6 +13,6 @@ export default defineConfig({
 });
 ```
 
-import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
-
-<RsbuildConfig configName="server.port" />
+:::info
+The usage of this configuration item is exactly the same as that of Rsbuild. For detailed information, please refer to [Rsbuild - server.port](https://v2.rsbuild.dev/config/server/port).
+:::

package/docs/configure/app/server/{public-routes.mdx → public-routes.md}

@@ -1,7 +1,3 @@
----
-title: publicRoutes
----
-
 # server.publicRoutes
 
 - **Type:** `Object`

package/docs/configure/app/server/{routes.mdx → routes.md}

@@ -1,7 +1,3 @@
----
-title: routes
----
-
 # server.routes
 
 - **Type:** `Object`
@@ -85,6 +81,6 @@ export default defineConfig({
 ```
 
 :::note
-This configuration takes effect in both the production and development environments, and different response headers can be set according to the NODE_ENV to distinguish between environments. However, if you only need to set response headers in the development environment, it is recommended to use `tools.devServer.headers`.
+This configuration takes effect in both the production and development environments, and different response headers can be set according to the NODE\_ENV to distinguish between environments. However, if you only need to set response headers in the development environment, it is recommended to use `tools.devServer.headers`.
 
 :::

package/docs/configure/app/server/{rsc.mdx → rsc.md}

@@ -1,7 +1,3 @@
----
-title: rsc
----
-
 # server.rsc
 
 - **Type:** `boolean`
@@ -21,10 +17,10 @@ export default defineConfig({
 
 :::tip Prerequisites
 Before enabling RSC, ensure:
+
 1. React and React DOM are upgraded to version 19 (recommended 19.2.4 or above)
 2. Install the `react-server-dom-rspack@0.0.2` dependency
 
 :::
 
-For more information about using RSC, see the [React Server Components guide](/guides/basic-features/render/rsc).
-
+For more information about using RSC, see the [React Server Components guide](/guides/basic-features/render/rsc.md).

package/docs/configure/app/server/{ssr-by-entries.mdx → ssr-by-entries.md}

@@ -1,13 +1,9 @@
----
-title: ssrByEntries
----
-
 # server.ssrByEntries
 
 - **Type:** `Object`
 - **Default:** `undefined`
 
-Set SSR options by entry, and the properties inside the option are the same as [ssr](./ssr.mdx). The specified value will be replaced and merged with the content of the SSR attribute, for example:
+Set SSR options by entry, and the properties inside the option are the same as [ssr](/configure/app/server/ssr.md). The specified value will be replaced and merged with the content of the SSR attribute, for example:
 
 :::info
 The "entry name" defaults to the directory name. In a few cases, when defining an entry through `source.entries`, the entry name is the `key` of the `source.entries` object.

package/docs/configure/app/server/ssr.md

@@ -0,0 +1,80 @@
+# server.ssr
+
+- **Type:** `boolean` | `Object`
+- **Default:** `false`
+
+Enable SSR configuration.
+
+### Boolean Type
+
+When the value type is `boolean`, it indicates whether to enable SSR deployment mode. The default is `false` to disable it.
+
+```ts title="modern.config.ts"
+export default defineConfig({
+  server: {
+    ssr: true,
+  },
+});
+```
+
+### Object Type
+
+When the value type is `Object`, the following properties can be configured:
+
+| Name                   | Type                            | Default         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| ---------------------- | ------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| mode                   | `string`                        | `stream`        | which defaults to using streaming rendering. Configure `string` to use `renderToString` for rendering                                                                                                                                                                                                                                                                                                                                                                                  |
+| forceCSR               | `boolean`                       | `false`         | which is off by default for forcing CSR rendering. Configure `true` to force CSR by adding `?csr=true` or adding `x-modern-ssr-fallback` header when accessing the page                                                                                                                                                                                                                                                                                                                |
+| unsafeHeaders          | `string[]`                      | `[]`            | For safety reasons, Modern.js does not add excessive content to SSR\_DATA. Developers can use this configuration to specify the headers that need to be injected                                                                                                                                                                                                                                                                                                                       |
+| loaderFailureMode      | `clientRender \| errorBoundary` | `errorBoundary` | The default configuration is `'errorBoundary'`, when an error occurs in [data loader](/guides/basic-features/data/data-fetch.md#data-loader-recommended), it will default to rendering the [`Error`](/guides/basic-features/routes/routes.md#error-handling) component of the route. When configured as `'clientRender'`, if a loader throws an error, it switch to client-side rendering，you can use it with [Client Loader](/guides/basic-features/data/data-fetch.md#client-loader) |
+| moduleFederationAppSSR | `boolean`                       | `false`         | Enables app-level Module Federation SSR contract handshake. Enable this in both host and remote apps when using app-level MF SSR                                                                                                                                                                                                                                                                                                                                                       |
+
+```ts title="modern.config.ts"
+export default defineConfig({
+  server: {
+    ssr: {
+      forceCSR: true,
+      mode: 'stream',
+      unsafeHeaders: ['User-Agent'],
+      moduleFederationAppSSR: true,
+    },
+  },
+});
+```
+
+### Active Fallback
+
+In a production environment, there are scenarios where it is necessary to actively fallback an SSR project to CSR. Examples include
+
+1. When the SSR fails, a fallback to the CSR is required to ensure product availability.
+
+2. When the SSR is working normally, but there are rendering failures during csr, debugging is required.
+
+3. When the SSR server is under heavy load, it may be necessary to fallback some traffic directly to the CSR to avoid service downtime.
+
+By configuring `server.ssr.forceCSR` to `true` in the project, you can control this behavior through query strings or request headers.
+
+For example, in a custom Web Server middleware, you can actively fallback when traffic exceeds a certain threshold:
+
+```ts title="server/modern.server.ts"
+import {
+  defineServerConfig,
+  type MiddlewareHandler,
+} from '@modern-js/server-runtime';
+
+export const handler: MiddlewareHandler = async (c, next) => {
+  if (condition) {
+    c.set('forceCSR', '1');
+  }
+  await next();
+};
+
+export default defineServerConfig({
+  middlewares: [
+    {
+      name: 'request-middleware',
+      handler,
+    },
+  ],
+});
+```