@bleedingdev/modern-js-main-doc 3.2.0-ultramodern.0

package/docs/en/configure/app/performance/remove-moment-locale.mdx

@@ -0,0 +1,14 @@
+---
+title: removeMomentLocale
+---
+
+# performance.removeMomentLocale
+
+- **Type:** `boolean`
+- **Default:** `false`
+
+Whether to remove the locales of [moment.js](https://momentjs.com/).
+
+import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
+
+<RsbuildConfig configName="performance.removeMomentLocale" />

package/docs/en/configure/app/performance/rsdoctor.mdx

@@ -0,0 +1,39 @@
+---
+title: rsdoctor
+---
+
+# performance.rsdoctor
+
+- **Type:**
+
+```ts
+type RsdoctorConfig =
+  | boolean
+  | {
+      enabled?: boolean;
+    };
+```
+
+- **Default:** `true` in production build, `false` in development mode.
+
+Configure Rsdoctor diagnostics in Modern.js build.
+
+```ts title="modern.config.ts"
+export default defineConfig({
+  performance: {
+    rsdoctor: false,
+  },
+});
+```
+
+You can also use object form:
+
+```ts title="modern.config.ts"
+export default defineConfig({
+  performance: {
+    rsdoctor: {
+      enabled: true,
+    },
+  },
+});
+```

package/docs/en/configure/app/plugins.mdx

@@ -0,0 +1,59 @@
+# plugins
+
+- **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).
+
+## 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.
+
+## Examples
+
+Below are examples of using CLI plugins:
+
+### Using plugins from npm
+
+To use plugins from the npm registry, first install the plugins and then import them in your configuration:
+
+```ts title="modern.config.ts"
+import { myPlugin } from 'my-plugin';
+
+export default defineConfig({
+  plugins: [myPlugin()],
+});
+```
+
+### Using local plugins
+
+To use plugins from your local repository, import them directly using a relative path:
+
+```ts title="modern.config.ts"
+import { myPlugin } from './config/plugin/myPlugin';
+
+export default defineConfig({
+  plugins: [myPlugin()],
+});
+```
+
+### Plugin configuration
+
+If a plugin provides custom configuration options, pass them as parameters to the plugin function:
+
+```ts title="modern.config.ts"
+import { myPlugin } from 'my-plugin';
+
+export default defineConfig({
+  plugins: [
+    myPlugin({
+      foo: 1,
+      bar: 2,
+    }),
+  ],
+});
+```

package/docs/en/configure/app/resolve/alias-strategy.mdx

@@ -0,0 +1,14 @@
+---
+title: aliasStrategy
+---
+
+# resolve.aliasStrategy
+
+- **Type:** `'prefer-tsconfig' | 'prefer-alias'`
+- **Default:** `'prefer-tsconfig'`
+
+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" />

package/docs/en/configure/app/resolve/alias.mdx

@@ -0,0 +1,13 @@
+---
+title: alias
+---
+
+# resolve.alias
+
+- **Type:** `string[]`
+
+Create aliases for module paths to simplify import paths or redirect module references.
+
+import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
+
+<RsbuildConfig configName="resolve.alias" />

package/docs/en/configure/app/resolve/condition-names.mdx

@@ -0,0 +1,18 @@
+---
+title: conditionNames
+---
+
+# resolve.conditionNames
+
+- **Type:** `string[]`
+- **Default:** Same as Rspack's `resolve.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" />
+
+:::warning
+Do not enable this configuration option for SSR applications, as it will cause SSR rendering to fail.
+:::

package/docs/en/configure/app/resolve/dedupe.mdx

@@ -0,0 +1,13 @@
+---
+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" />

package/docs/en/configure/app/resolve/extensions.mdx

@@ -0,0 +1,18 @@
+---
+title: extensions
+---
+
+# resolve.extensions
+
+- **Type:** `string[]`
+- **Default:** `['.ts', '.tsx', '.mjs', '.js', '.jsx', '.json']`
+
+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" />
+
+:::warning
+Do not enable this configuration option for SSR applications, as it will cause SSR rendering to fail.
+:::

package/docs/en/configure/app/runtime/0-intro.mdx

@@ -0,0 +1,61 @@
+# Introduce
+
+Modern.js runtime configuration should be centralized in the `src/modern.runtime.ts` file.
+
+:::info
+
+If this file doesn't exist in your project yet, create it with the following command:
+
+```bash
+touch src/modern.runtime.ts
+```
+
+:::
+
+## Basic Configuration
+
+```tsx
+import { defineRuntimeConfig } from '@modern-js/runtime';
+
+export default defineRuntimeConfig({
+  router: {
+    // Router configuration
+  },
+  // Other runtime modules...
+});
+```
+
+## Multi-Entry Configuration
+
+For multi-entry applications, `defineRuntimeConfig` can accept a function that returns specific configurations based on the entry name:
+
+```tsx
+import { defineRuntimeConfig } from '@modern-js/runtime';
+
+export default defineRuntimeConfig(entryName => {
+  if (entryName === 'main') {
+    return {
+      router: {
+        // Router configuration for "main" entry
+      },
+    };
+  }
+
+  // Configuration for other entries
+  return {
+    router: {
+      // Other entry router configuration
+    },
+  };
+});
+```
+
+:::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)**.
+
+:::
+
+import RuntimeCliConfig from '@site-docs/components/runtime-cli-config';
+
+<RuntimeCliConfig />

package/docs/en/configure/app/runtime/plugins.mdx

@@ -0,0 +1,58 @@
+# plugins
+
+- **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).
+
+:::info
+
+Runtime plugins must be configured in the `plugins` array within the `src/modern.runtime.ts` file.
+
+:::
+
+## Examples
+
+Here are examples demonstrating how to use Runtime plugins:
+
+### Using plugins from npm packages
+
+To use plugins published on npm, first install them via your package manager, then import them into your configuration.
+
+```ts title="src/modern.runtime.ts"
+import { defineRuntimeConfig } from '@modern-js/runtime';
+import { myPlugin } from 'my-plugin';
+
+export default defineRuntimeConfig({
+  plugins: [myPlugin()],
+});
+```
+
+### Using local plugins
+
+To use plugins from your local codebase, import them directly using relative paths.
+
+```ts title="src/modern.runtime.ts"
+import { defineRuntimeConfig } from '@modern-js/runtime';
+import { myPlugin } from './config/plugin/myPlugin';
+
+export default defineRuntimeConfig({
+  plugins: [myPlugin()],
+});
+```
+
+### Plugin configuration
+
+If a plugin supports custom configuration options, you can provide them as arguments to the plugin function.
+
+```ts title="src/modern.runtime.ts"
+import { defineRuntimeConfig } from '@modern-js/runtime';
+import { myPlugin } from './config/plugin/myPlugin';
+
+export default defineRuntimeConfig({
+  plugins: [myPlugin({
+    foo: 1,
+    bar: 2,
+  })],
+});
+```

package/docs/en/configure/app/runtime/router.mdx

@@ -0,0 +1,39 @@
+---
+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.
+
+:::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).
+:::
+
+## basename
+
+- **Type:** `string`
+- **Default:** `/`
+
+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.
+:::
+
+## supportHtml5History
+
+- **Type:** `boolean`
+- **Default:** `true`
+
+If the value of `supportHtml5History` is `true`, `BrowserRouter` would be used, otherwise `HashRouter` would be used. `BrowserRouter` is recommended.
+
+:::warning
+When SSR is enabled, `supportHtml5History` is not supported.
+
+:::

package/docs/en/configure/app/security/check-syntax.mdx

@@ -0,0 +1,73 @@
+---
+title: checkSyntax
+---
+
+# security.checkSyntax
+
+- **Type:**
+
+```ts
+type CheckSyntax =
+  | boolean
+  | {
+      targets?: string[];
+      exclude?: RegExp | RegExp[];
+      ecmaVersion?: EcmaVersion;
+    };
+```
+
+- **Default:** `false`
+
+Used to analyze whether there is incompatible advanced syntax in the build artifacts under the current browser scope. If any incompatible syntax is found, detailed information will be printed to the terminal.
+
+### Enable Detection
+
+You can set `checkSyntax` to `true` to enable syntax checking.
+
+```ts
+export default {
+  security: {
+    checkSyntax: true,
+  },
+};
+```
+
+When you enable `checkSyntax`, Modern.js will perform the detection during production builds. If any incompatible advanced syntax is detected in the build artifacts, error logs will be printed to the terminal, and the current build process will be terminated.
+
+### Error Logs
+
+The format of the error logs is as follows, including the source file, artifact location, error reason, and source code:
+
+```bash
+error   [Syntax Checker] Find some syntax errors after production build:
+
+  Error 1
+  source:  /node_modules/foo/index.js:1:0
+  output:  /dist/static/js/main.3f7a4d7e.js:2:39400
+  reason:  Unexpected token (1:178)
+  code:
+     9 |
+    10 | var b = 2;
+    11 |
+  > 12 | console.log(() => {
+    13 |   return a + b;
+    14 | });
+    15 |
+```
+
+:::tip
+Currently, syntax checking is implemented based on AST parser. Each time it performs a check, it can only identify the first incompatible syntax found in the file. If there are multiple incompatible syntaxes in the file, you need to fix the detected syntax and re-run the check.
+If the corresponding source location is not shown in the log, try setting **output.minify** to false and rebuild again.
+:::
+
+### Solutions
+
+If a syntax error is detected, you can handle it in the following ways:
+
+- If you want to downgrade this syntax to ensure good code compatibility, you can compile the corresponding module through the `source.include` config.
+- If you don't want to downgrade the syntax, you can adjust the project's browserslist to match the syntax.
+- If you do not want to check the syntax of certain products, you can use the `checkSyntax.exclude` configuration to exclude the files to be checked.
+
+### Options
+
+`security.checkSyntax` is implemented based on `@rsbuild/plugin-check-syntax`. For specific options, please refer to [@rsbuild/plugin-check-syntax](https://github.com/rspack-contrib/rsbuild-plugin-check-syntax).

package/docs/en/configure/app/security/nonce.mdx

@@ -0,0 +1,19 @@
+---
+title: nonce
+---
+
+# security.nonce
+
+- **Type:**
+
+```ts
+type Nonce = string;
+```
+
+- **Default:** `undefined`
+
+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" />

package/docs/en/configure/app/security/sri.mdx

@@ -0,0 +1,24 @@
+---
+title: sri
+---
+
+# security.sri
+
+- **Type**
+
+```ts
+type SriOptions = {
+  hashFuncNames?: [string, ...string[]];
+  enabled?: 'auto' | true | false;
+};
+```
+
+- **Default:** `undefined`
+
+Adding an `integrity` attribute to `<script>` and `<link rel="stylesheet">` tags introduced by HTML allows the browser to verify the integrity of the introduced resource, thus preventing tampering with the downloaded resource.
+
+:::info
+For a specific introduction to SRI, you can refer to [Rsbuild security.sri](https://v2.rsbuild.rs/zh/config/security/sri).
+
+This configuration type is not completely consistent with Rsbuild and will be automatically converted during the build process.
+:::

package/docs/en/configure/app/server/base-url.mdx

@@ -0,0 +1,30 @@
+---
+title: baseUrl
+---
+
+# server.baseUrl
+
+- **Type:** `string | string[]`
+- **Default:** `undefined`
+
+Uniformly set the prefix of server-side routes (commonly used in situations where multiple applications share the same domain name to distinguish traffic).
+
+```ts title="modern.config.ts"
+export default defineConfig({
+  server: {
+    // All generated routes will automatically have the prefix `/base`
+    // Generated server-side route file path: dist/route.json
+    baseUrl: '/base'
+
+    // Multiple baseUrl
+    baseUrl: ['/base-new', '/base-old']
+  }
+})
+```
+
+After running `dev`, you will see that the route access will have the corresponding prefix added:
+
+```bash
+  > Local:    http://localhost:8080/base/
+  > Network:  http://192.168.0.1:8080/base/
+```

package/docs/en/configure/app/server/port.mdx

@@ -0,0 +1,22 @@
+---
+title: port
+---
+
+# server.port
+
+- **Type:** `number`
+- **Default:** `8080`
+
+When running the `dev` and `serve` commands, Modern.js will start with `8080` as the default port and automatically increase the port number when the port is occupied. You can use this configuration to modify the port number that the Server starts with:
+
+```js title="modern.config.ts"
+export default defineConfig({
+  server: {
+    port: 3000,
+  },
+});
+```
+
+import RsbuildConfig from '@site-docs-en/components/rsbuild-config-tooltip';
+
+<RsbuildConfig configName="server.port" />

package/docs/en/configure/app/server/public-routes.mdx

@@ -0,0 +1,26 @@
+---
+title: publicRoutes
+---
+
+# server.publicRoutes
+
+- **Type:** `Object`
+- **Default:** Server-side routing rules generated based on file conventions, with one route rule generated for each file.
+
+This configuration option only applies to server-side routing and can customize the access route of resources under `config/public/`.
+
+The `key` of the object is the relative file path of the `config/public/` (without using `./`), and the value can be a `string`.
+
+```ts title="modern.config.ts"
+export default defineConfig({
+  server: {
+    publicRoutes: {
+      // Set a long route
+      'index.json': '/user-config/card-info/extra/help.json',
+
+      // Set a route without a suffix
+      'robot.txt': '/app/authentication',
+    },
+  },
+});
+```

package/docs/en/configure/app/server/routes.mdx

@@ -0,0 +1,90 @@
+---
+title: routes
+---
+
+# server.routes
+
+- **Type:** `Object`
+- **Default:** Server-side routing rules generated based on file conventions, with one route rule generated for each entry, and the entry name is equal to the route path.
+
+This configuration option only applies to server-side routing and can customize the access route of application entries.
+
+## Custom access routes
+
+The `key` of the object is the name of the current application entry, and the value can be a `string | Array<string>`.
+
+When the value type is `string`, the current value represents the route path for accessing the entry.
+
+```ts title="modern.config.ts"
+export default defineConfig({
+  server: {
+    routes: {
+      // Default route is /entryName1, customized to /p/test1
+      entryName1: '/p/test1'
+      // Supports dynamic server-side routing configuration
+      entryName2: '/detail/:id'
+    }
+  }
+});
+```
+
+Multiple access routes can also be set for the entry through `Array<string>`:
+
+```ts title="modern.config.ts"
+export default defineConfig({
+  server: {
+    routes: {
+      'page-a': [`/a`, '/b'],
+    },
+  },
+});
+```
+
+At this time, the `page-a` entry can be accessed through both the `/a` and `/b` routes.
+
+After executing the `dev` command, you can view two route records for the `page-a` entry in `dist/route.json`:
+
+```json
+{
+  "routes": [
+    {
+      "urlPath": "/a",
+      "entryName": "page-a",
+      "entryPath": "html/page-a/index.html",
+      "isSPA": true,
+      "isSSR": false
+    },
+    {
+      "urlPath": "/b",
+      "entryName": "page-a",
+      "entryPath": "html/page-a/index.html",
+      "isSPA": true,
+      "isSSR": false
+    }
+  ]
+}
+```
+
+## Custom response headers
+
+Response headers can be set by configuring the `resHeaders` of the entry:
+
+```ts title="modern.config.ts"
+export default defineConfig({
+  server: {
+    routes: {
+      'page-a': {
+        route: ['/a', '/b'],
+        resHeaders: {
+          'x-modern-test': '1',
+        },
+      },
+    },
+  },
+});
+```
+
+:::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`.
+
+:::

package/docs/en/configure/app/server/rsc.mdx

@@ -0,0 +1,30 @@
+---
+title: rsc
+---
+
+# server.rsc
+
+- **Type:** `boolean`
+- **Default:** `false`
+
+Enable React Server Components (RSC) configuration.
+
+When set to `true`, enables React Server Components support in Modern.js. This allows components to be rendered on the server, providing better performance and developer experience.
+
+```ts title="modern.config.ts"
+export default defineConfig({
+  server: {
+    rsc: true,
+  },
+});
+```
+
+:::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.1-beta.1` dependency
+
+:::
+
+For more information about using RSC, see the [React Server Components guide](/guides/basic-features/render/rsc).
+