@modern-js/main-doc 3.1.5 → 3.2.0

package/docs/en/guides/advanced-features/international/routing.mdx

@@ -4,149 +4,101 @@ title: Routing Integration
 
 # Routing Integration
 
-The plugin is deeply integrated with Modern.js routing system, supporting language path prefixes and automatic path redirection.
+## Enable Locale Path Prefixes
 
-## Enable Path Redirection
+After setting `localePathRedirect: true`, the plugin takes over language recognition and navigation in the URL. It does four things:
 
-When `localePathRedirect` is set to `true`, the plugin will automatically add language prefixes to URLs and handle path redirection when switching languages.
-
-**Configuration**:
+1. **Recognizes the locale prefix in the URL**: When visiting `/zh/detail`, the plugin extracts `zh` from the path as the current language.
+2. **Automatically redirects paths without prefixes**: When visiting `/detail`, it first detects the language with the detector. If detection fails, it uses `fallbackLanguage`, then redirects to `/en/detail` or `/zh/detail`.
+3. **Synchronizes the URL when switching language**: If the current URL is `/en/detail`, calling `changeLanguage('zh')` automatically changes the URL to `/zh/detail`, instead of only changing i18next's internal language state.
+4. **Avoids duplicate path detection**: The plugin automatically removes `path` from the i18next detector `order`, because path language recognition is already handled by the plugin itself.
 
 ```ts
+// modern.config.ts
 i18nPlugin({
   localeDetection: {
     localePathRedirect: true,
     languages: ['zh', 'en'],
     fallbackLanguage: 'en',
-    // Optional: ignore automatic redirection for certain routes
-    ignoreRedirectRoutes: ['/api', '/admin'],
   },
 });
 ```
 
-### Ignore Redirection Routes
-
-Some routes (such as API routes, static resources, etc.) don't need language prefixes. You can use the `ignoreRedirectRoutes` configuration to ignore automatic redirection for these routes:
+**Result:**
 
-```ts
-i18nPlugin({
-  localeDetection: {
-    localePathRedirect: true,
-    languages: ['zh', 'en'],
-    fallbackLanguage: 'en',
-    // String array: supports exact match and prefix match
-    ignoreRedirectRoutes: ['/api', '/admin', '/static'],
-    // Or use function for more flexible judgment
-    ignoreRedirectRoutes: pathname => {
-      return pathname.startsWith('/api') || pathname.startsWith('/admin');
-    },
-  },
-});
-```
+| Visited path | Result |
+| --- | --- |
+| `/about` | Redirects to `/en/about` |
+| `/en/about` | Visits normally, language is `en` |
+| `/zh/about` | Visits normally, language is `zh` |
 
-For more details, please refer to the `ignoreRedirectRoutes` configuration in the [Locale Detection documentation](./locale-detection#ignoreredirectroutes).
+Some paths, such as API routes and static assets, do not need locale prefixes. Use `ignoreRedirectRoutes` to skip redirects. See [Locale Detection -> ignoreRedirectRoutes](./locale-detection.md#ignoreredirectroutes).
 
 ## Route Configuration
 
-After enabling path redirection, you need to add `:lang` dynamic parameter to the route configuration.
+After enabling `localePathRedirect`, add a `[lang]` dynamic parameter in routes to receive the locale prefix.
 
-### Convention-based Routing
+### File-system Routes
 
-When using convention-based routing, you need to create a `[lang]` directory under the `routes/` directory to represent the language parameter:
+Create a `[lang]` directory under `routes/`:
 
-```bash
+```
 routes/
-├── [lang]/
-│   ├── layout.tsx    # Layout component
-│   ├── page.tsx      # Home page
-│   ├── about/
-│   │   └── page.tsx  # About page
-│   └── contact/
-│       └── page.tsx  # Contact page
+└── [lang]/
+    ├── layout.tsx    <- You can read params.lang here.
+    ├── page.tsx
+    └── about/
+        └── page.tsx
 ```
 
-**routes/[lang]/layout.tsx**:
-
-```tsx
-import { Outlet } from '@modern-js/runtime/router';
+Generated route structure:
 
-export default function Layout() {
-  return <Outlet />;
-}
 ```
-
-**routes/[lang]/page.tsx**:
-
-```tsx
-export default function Home() {
-  return <div>Home</div>;
-}
+/:lang          -> page.tsx
+/:lang/about    -> about/page.tsx
 ```
 
-**routes/[lang]/about/page.tsx**:
+If you need to read the current language parameter in a layout or page:
 
 ```tsx
-export default function About() {
-  return <div>About</div>;
-}
-```
-
-**routes/[lang]/contact/page.tsx**:
+// routes/[lang]/layout.tsx
+import { Outlet, useParams } from '@modern-js/runtime/router';
 
-```tsx
-export default function Contact() {
-  return <div>Contact</div>;
+export default function Layout() {
+  const { lang } = useParams();
+  // lang is the language code in the current URL, such as 'en' or 'zh'.
+  // Usually you do not need to use it manually. useModernI18n() manages it automatically.
+  return <Outlet />;
 }
 ```
 
-**Generated Route Structure**:
+### Custom Routes
 
-```
-/:lang          → Home page
-/:lang/about    → About page
-/:lang/contact  → Contact page
-```
-
-When accessing `/` or `/about`, it will automatically redirect to `/en` or `/en/about` (using the default language).
-
-### Custom Routing
+:::info
+Custom routes are only needed when you are not using the Modern.js file-system routing system. File-system routes are recommended for most projects.
+:::
 
-If using custom routing (`modern.routes.ts`), you need to add `:lang` dynamic parameter in the route configuration:
+If you use a custom route file (`modern.routes.ts`), add the `:lang` parameter manually:
 
 ```tsx
-import {
-  BrowserRouter,
-  Route,
-  Routes,
-  Outlet,
-} from '@modern-js/runtime/router';
-
-function App() {
+// modern.routes.ts
+import { Route, Routes, Outlet } from '@modern-js/runtime/router';
+
+export default function App() {
   return (
-    <BrowserRouter>
-      <Routes>
-        {/* Add :lang parameter */}
-        <Route path=":lang" element={<Outlet />}>
-          <Route index element={<Home />} />
-          <Route path="about" element={<About />} />
-          <Route path="contact" element={<Contact />} />
-        </Route>
-      </Routes>
-    </BrowserRouter>
+    <Routes>
+      <Route path=":lang" element={<Outlet />}>
+        <Route index element={<Home />} />
+        <Route path="about" element={<About />} />
+      </Route>
+    </Routes>
   );
 }
 ```
 
-:::info
-Convention-based routing will automatically generate corresponding routes based on the file structure. It's recommended to use convention-based routing. Only use custom routing when special route control is needed.
-
-:::
-
 ## I18nLink Component
 
-The `I18nLink` component is provided by `@modern-js/plugin-i18n` and automatically adds the current language prefix to paths.
-
-### Basic Usage
+`I18nLink` is a locale-aware link component. It automatically adds the current locale prefix to the target path, so you do not need to concatenate it manually.
 
 ```tsx
 import { I18nLink } from '@modern-js/plugin-i18n/runtime';
@@ -156,57 +108,27 @@ function Navigation() {
     <nav>
       <I18nLink to="/">Home</I18nLink>
       <I18nLink to="/about">About</I18nLink>
-      <I18nLink to="/contact">Contact</I18nLink>
+      <I18nLink to="/contact" replace>Contact</I18nLink>
     </nav>
   );
 }
 ```
 
-**When current language is `en`**:
-
-- `<I18nLink to="/">` → Actual link: `/en`
-- `<I18nLink to="/about">` → Actual link: `/en/about`
-
-**When current language is `zh`**:
+**When the current language is `en`:**
 
-- `<I18nLink to="/">` → Actual link: `/zh`
-- `<I18nLink to="/about">` → Actual link: `/zh/about`
-
-### Automatic Language Prefix
+```
+<I18nLink to="/about">  ->  Actual link: /en/about
+<I18nLink to="/">       ->  Actual link: /en
+```
 
-`I18nLink` automatically handles language prefixes, no need to add them manually:
+**Notes:**
 
 ```tsx
-// ✅ Correct: No need to manually add language prefix
+// Correct: no need to add the locale prefix manually.
 <I18nLink to="/about">About</I18nLink>
 
-// ❌ Wrong: Don't manually add language prefix
+// Incorrect: do not add the locale prefix manually, or it becomes /en/en/about.
 <I18nLink to="/en/about">About</I18nLink>
 ```
 
-### Props
-
-`I18nLink` accepts all `Link` component props and additionally supports:
-
-```tsx
-interface I18nLinkProps {
-  /** Target path (no need to include language prefix) */
-  to: string;
-  /** Child elements */
-  children: React.ReactNode;
-  /** Other Link component props */
-  [key: string]: any;
-}
-```
-
-**Example**:
-
-```tsx
-<I18nLink to="/about" replace>
-  About
-</I18nLink>
-
-<I18nLink to="/contact" state={{ from: 'home' }}>
-  Contact
-</I18nLink>
-```
+`I18nLink` extends the `Link` component from `@modern-js/runtime/router` and supports all standard Link props such as `replace`, `state`, and `className`. For the full Props type, see [API Reference](./api.md#i18nlink-component).

package/docs/en/guides/advanced-features/international.mdx

@@ -8,30 +8,22 @@ import I18nPluginIntroduce from '@site-docs/components/international/introduce';
 
 <I18nPluginIntroduce />
 
-## Core Features
-
-- 🌍 **Multi-language Support**: Easily manage translation resources for multiple languages
-- 🔍 **Smart Language Detection**: Supports automatic language detection from URL paths, cookies, request headers, and more
-- 📦 **Flexible Resource Loading**: Supports three resource loading methods: HTTP, file system, and custom SDK
-- 🛣️ **Route Integration**: Deeply integrated with Modern.js routing system, supports language path prefixes
-- ⚡ **SSR Support**: Full support for server-side rendering (SSR) scenarios
-- 🎯 **TypeScript Support**: Complete TypeScript type definitions
-
-## Use Cases
-
-- Web applications that need to support multiple languages
-- Multi-language routing that is SEO-friendly
-- Multi-language applications that require server-side rendering
-- Applications that need to dynamically load translation resources from external services
-
-## Documentation Navigation
-
-- [Basic Concepts](./international/basic) - Core concepts and terminology
-- [Quick Start](./international/quick-start) - Detailed installation and configuration guide
-- [Configuration](./international/configuration) - CLI and runtime configuration details
-- [Locale Detection](./international/locale-detection) - Multiple language detection methods and priorities
-- [Resource Loading](./international/resource-loading) - HTTP, FS, and SDK backend usage
-- [Routing Integration](./international/routing) - Path redirection and I18nLink component
-- [API Reference](./international/api) - Complete API documentation and type definitions
-- [Advanced Usage](./international/advanced) - SSR, multi-entry, custom instances, and more
-- [Best Practices](./international/best-practices) - Resource organization, error handling, type safety
+## Where to start?
+
+| What you want to do | Documentation |
+| --- | --- |
+| Integrate for the first time and run an example | [Quick Start](./international/quick-start.md) |
+| Learn all configuration options | [Configuration](./international/configuration.md) |
+| Detect language from URL / Cookie / Header | [Locale Detection](./international/locale-detection.md) |
+| Implement paths with locale prefixes, such as `/en/about` | [Routing Integration](./international/routing.md) |
+| Load translation resources from a remote service or platform | [Resource Loading -> Custom Backend](./international/resource-loading.md#custom-backend) |
+| SSR, multiple entries, or custom instances | [Advanced Usage](./international/advanced.md) |
+| Look up Hooks / components / type definitions | [API Reference](./international/api.md) |
+
+## Core Capabilities
+
+- **Locale detection**: Supports detection from URL path, Cookie, LocalStorage, request headers, browser settings, and other sources, with configurable priority.
+- **Resource loading**: Supports HTTP static files, file system loading for SSR, custom SDK functions, and chained backend progressive loading.
+- **Routing integration**: Automatically adds locale path prefixes such as `/en/about`, and provides the `I18nLink` component for locale-aware navigation.
+- **SSR support**: Detects the language on the server and injects it into the page so the client can reuse it directly and avoid language flicker.
+- **TypeScript support**: Provides complete type definitions and supports type-safe translation keys.

package/docs/en/guides/basic-features/alias.mdx

@@ -37,7 +37,7 @@ You can refer to the [TypeScript - paths](https://www.typescriptlang.org/tsconfi
 
 ## Use `source.alias` Configuration
 
-Modern.js provides the [source.alias](/configure/app/source/alias) configuration option, which corresponds to the webpack/Rspack native [resolve.alias](https://webpack.js.org/configuration/resolve/#resolvealias) configuration. You can configure this option using an object or a function.
+Modern.js provides the [source.alias](/configure/app/source/alias) configuration option. You can configure this option using an object or a function.
 
 ### Use Cases
 

package/docs/en/guides/basic-features/html.mdx

@@ -190,7 +190,7 @@ Under the application root directory, create the `config/html/` directory, which
   <head>
     <%= topTemplate %>
     <%= headTemplate %>
-    {/* webpack inject css  */}
+    {/* rspack inject css  */}
   </head>
   <body>
     <noscript>
@@ -199,7 +199,7 @@ Under the application root directory, create the `config/html/` directory, which
     </noscript>
     <div id="<%= mountId %>"></div>
     <%= bodyTemplate %>
-    {/* webpack inject js  */}
+    {/* rspack inject js  */}
     {/* <?- bottomTemplate ?> */}
   </body>
 </html>

package/docs/en/guides/basic-features/static-assets.mdx

@@ -123,7 +123,7 @@ After adding the type declaration, if the type error still exists, you can try t
 
 ## Extend Asset Types
 
-If the built-in asset types in Modern.js cannot meet your requirements, you can modify the built-in webpack/Rspack configuration and extend the asset types you need using [tools.bundlerChain](/configure/app/tools/bundler-chain).
+If the built-in asset types in Modern.js cannot meet your requirements, you can modify the built-in Rspack configuration and extend the asset types you need using [tools.bundlerChain](/configure/app/tools/bundler-chain).
 
 For example, if you want to treat `*.pdf` files as assets and directly output them to the dist directory, you can add the following configuration:
 
@@ -151,7 +151,6 @@ console.log(myFile); // "/static/myFile.6c12aba3.pdf"
 For more information about asset modules, please refer to:
 
 - [Rspack Documentation - Asset modules](https://rspack.rs/guide/asset-module.html#asset-modules)
-- [webpack Documentation - Asset modules](https://webpack.js.org/guides/asset-modules/)
 
 ## Image Format
 

package/docs/en/guides/concept/entries.mdx

@@ -273,13 +273,13 @@ export default defineConfig({
 
 ## In-Depth
 
-The concept of page entry is derived from the concept of [Entrypoint](https://webpack.js.org/concepts/entry-points/) in webpack. It is mainly used to configure JavaScript or other modules to be executed during application startup. webpack's [best practice](https://webpack.docschina.org/concepts/entry-points/#multi-page-application) for web applications usually corresponds entries to HTML output files, meaning each additional entry will eventually generate a corresponding HTML file in the output. The modules imported by the entry will be compiled and packaged into multiple Chunk outputs. For example, JavaScript modules may ultimately generate several file outputs similar to `dist/static/js/index.ea39u8.js`.
+Pages usually correspond to HTML output files, meaning each additional entry will eventually generate a corresponding HTML file in the output. The modules imported by the entry will be compiled and packaged into multiple Chunk outputs. For example, JavaScript modules may ultimately generate several file outputs similar to `dist/static/js/index.ea39u8.js`.
 
 It's important to distinguish the relationships between concepts such as entry and route:
 
 - **Entry**: Contains multiple modules used for startup execution.
 - **Client Router**: In Modern.js, it is usually implemented by `react-router`, using the History API to determine which React component to load and display based on the browser's current URL.
-- **Server Router**: The server can mimic [devServer behavior](https://webpack.docschina.org/configuration/dev-server/#devserverhistoryapifallback), returning the index.html page instead of all 404 responses to implement client-side routing, or it can implement any routing logic as needed.
+- **Server Router**: Determines what content the server returns based on the request URL. For traditional multi-page applications, different URLs usually return different HTML pages directly. For single-page applications that use client-side routing, the server generally falls back non-static asset requests to the entry HTML, and then the frontend takes over subsequent route matching and page rendering.
 
 Their corresponding relationships are as follows:
 

package/docs/zh/components/international/init-options-desc.mdx

@@ -1 +1 @@
-`initOptions` 会传递给 i18next 的 `init` 方法，支持所有 i18next 配置选项：
+支持所有 [i18next 初始化选项](https://www.i18next.com/overview/configuration-options)，常用选项说明如下：

package/docs/zh/components/international/install-command.mdx

@@ -1,23 +1,11 @@
-```bash
-pnpm add @modern-js/plugin-i18n i18next react-i18next
-```
+`i18next` 和 `react-i18next` 是 **Peer Dependency**，需要手动安装。
 
-:::tip 版本一致性
-请确保 `@modern-js/plugin-i18n` 的版本与项目中 `@modern-js/app-tools` 的版本一致。所有 Modern.js 官方包都使用统一的版本号发布，版本不匹配可能会导致兼容性问题。
+:::note 版本一致性
+`@modern-js/plugin-i18n` 需要与项目中 `@modern-js/app-tools` 版本保持一致。
+:::
 
-请先检查 `@modern-js/app-tools` 的版本，然后安装相同版本的 `@modern-js/plugin-i18n`：
 
 ```bash
-# 检查当前 @modern-js/app-tools 的版本
 pnpm list @modern-js/app-tools
-
-# 安装相同版本的 @modern-js/plugin-i18n
 pnpm add @modern-js/plugin-i18n@<version> i18next react-i18next
 ```
-
-:::
-
-:::info
-`i18next` 和 `react-i18next` 是 peer dependencies，需要手动安装。
-
-:::

package/docs/zh/components/international/instance-code.mdx

@@ -1,26 +1,16 @@
-创建 `src/modern.runtime.ts` 文件并配置 i18n 运行时选项：
+创建 `src/modern.runtime.ts`：
 
 ```ts
 import { defineRuntimeConfig } from '@modern-js/runtime';
 import i18next from 'i18next';
 
-// 建议创建一个新的 i18next 实例，避免使用全局默认实例
+// i18next 默认导出一个全局单例，多个应用共用会互相影响。
+// createInstance() 创建独立实例，确保每个应用有独立的语言状态。
 const i18nInstance = i18next.createInstance();
 
 export default defineRuntimeConfig({
   i18n: {
-    i18nInstance: i18nInstance,
-    initOptions: {
-      fallbackLng: 'en',
-      supportedLngs: ['zh', 'en'],
-    },
+    i18nInstance,
   },
 });
 ```
-
-:::info
-`modern.runtime.ts` 是运行时配置文件，用于配置 i18next 的初始化选项。即使是最基础的配置，也建议创建此文件以确保插件正常工作。
-
-建议使用 `i18next.createInstance()` 创建一个新的实例，而不是直接使用默认导出的 `i18next`，这样可以避免全局状态污染，并确保每个应用都有独立的 i18n 实例。
-
-:::

package/docs/zh/components/international/introduce.mdx

@@ -1,2 +1,5 @@
-`@modern-js/plugin-i18n` 是 Modern.js 的国际化插件，基于
-[i18next](https://www.i18next.com/) 和 [react-i18next](https://react.i18next.com/) 构建，为 Modern.js 应用提供完整的国际化解决方案。
+`@modern-js/plugin-i18n` 是 Modern.js 的国际化插件，基于 [i18next](https://www.i18next.com/) 和 [react-i18next](https://react.i18next.com/) 构建。
+
+- **插件本身**：负责与 Modern.js 框架的集成，如 SSR 语言传递、路由前缀处理等
+- **i18next**：核心翻译能力，如 `t()` 函数、插值、复数、命名空间。
+- **react-i18next**：React 组件和 Hook，如 `useTranslation`，实现与 React 生命周期的结合。

package/docs/zh/configure/app/source/enable-async-pre-entry.mdx

@@ -0,0 +1,77 @@
+---
+title: enableAsyncPreEntry
+---
+
+# source.enableAsyncPreEntry
+
+- **类型：** `boolean`
+- **默认值：** `false`
+
+开启后，Modern.js 会在自动生成的入口文件（`index.jsx`）最上方依次插入 `source.preEntry` 中配置的模块 import。
+
+该配置仅在 `source.enableAsyncEntry` 开启时生效；如果未开启异步入口，则不会启用该行为（并保持 `source.preEntry` 原有的构建器注入逻辑不受影响）。
+
+该配置主要用于配合 `source.enableAsyncEntry` 使用：当启用异步入口时，最终的构建 entry 会变为 `bootstrap.jsx`，这会导致构建器侧的 `source.preEntry` 不一定能注入到真正的入口代码中。开启 `source.enableAsyncPreEntry` 后，`preEntry` 会注入到 `index.jsx`（真正的入口代码）顶部，从而保证在异步入口场景下也能生效。
+
+同时，当 `source.enableAsyncPreEntry` 开启时，Modern.js 不会将 `source.preEntry` 传递给构建器配置，避免重复注入或注入到不期望的 entry 中。
+
+## 示例
+
+```ts title="modern.config.ts"
+import { defineConfig } from '@modern-js/app-tools';
+
+export default defineConfig({
+  source: {
+    enableAsyncEntry: true,
+    enableAsyncPreEntry: true,
+    preEntry: ['./src/pre-a.ts', './src/pre-b.ts'],
+  },
+});
+```
+
+## 编译效果
+
+在开启 `source.enableAsyncEntry` 后，Modern.js 会为每个入口生成一个异步边界文件 `bootstrap.jsx`，并由它去动态加载真正的入口代码 `index.jsx`。
+
+当同时开启 `source.enableAsyncPreEntry` 时，Modern.js 会把 `source.preEntry` 以 `import` 的形式注入到 **`index.jsx` 的最顶部**（而不是注入到 `bootstrap.jsx`），保证异步入口场景下 `preEntry` 一定会在入口代码之前执行。
+
+### 生成文件结构
+
+以单入口 `main` 为例，生成的文件结构大致如下（位于 `node_modules/.modern-js/main/`）：
+
+```bash
+node_modules
+  └─ .modern-js
+     └─ main
+        ├─ bootstrap.jsx        # 最终用于构建的 entry（异步边界）
+        ├─ index.jsx            # 真正的入口代码（会被注入 preEntry import）
+        ├─ register.js
+        ├─ runtime-register.js
+        └─ runtime-global-context.js
+```
+
+### bootstrap.jsx
+
+`bootstrap.jsx` 的核心逻辑是通过 dynamic import 加载 `index.jsx`：
+
+```js title="node_modules/.modern-js/main/bootstrap.jsx"
+import(/* webpackChunkName: "async-main" */ './index');
+```
+
+### index.jsx（会注入 preEntry）
+
+开启 `source.enableAsyncPreEntry` 后，`index.jsx` 文件的最上方会被注入 `source.preEntry` 对应的 import，随后才是 Modern.js 生成的入口逻辑，例如：
+
+```js title="node_modules/.modern-js/main/index.jsx"
+import '@_modern_js_src/pre-a.ts';
+import '@_modern_js_src/pre-b.ts';
+
+import '@modern-js/runtime/registry/main';
+// ...后续为 Modern.js 自动生成的入口逻辑
+```
+
+其中 `@_modern_js_src` 是 Modern.js 内部用于指向项目 `src` 目录的别名（实际值会随项目 metaName 等信息变化）。
+
+### 与 builder 的关系
+
+当 `source.enableAsyncEntry` 与 `source.enableAsyncPreEntry` 同时开启时，Modern.js **不会再把 `source.preEntry` 传递给构建器配置**，避免构建器重复注入或注入到不期望的 entry 中。

package/docs/zh/configure/app/tools/dev-server.mdx

@@ -9,10 +9,6 @@ title: devServer
 
 通过 `tools.devServer` 可以修改开发环境服务器的配置。
 
-:::tip
-Modern.js 中并没有直接使用 [webpack-dev-server](https://webpack.js.org/api/webpack-dev-server/) 或 [@rspack/dev-server](https://rspack.rs/guide/dev-server.html), 而是基于 [webpack-dev-middleware](https://github.com/webpack/webpack-dev-middleware) 实现 DevServer。
-:::
-
 ### 选项
 
 #### compress

package/docs/zh/guides/advanced-features/bff/function.mdx

@@ -188,7 +188,7 @@ Dynamic Path 之后的参数是包含 querystring、request body 的对象 `Requ
 在不存在动态路由的普通函数中，可以从第一个入参中获取传入的 `data` 和 `query`，例如：
 
 ```ts title="api/lambda/hello.ts"
-import type { RequestOption } from '@modern-js/server-runtime';
+import type { RequestOption } from '@modern-js/plugin-bff/server';
 
 export async function post({
   query,
@@ -201,7 +201,7 @@ export async function post({
 这里你也可以使用自定义类型：
 
 ```ts title="api/lambda/hello.ts"
-import type { RequestOption } from '@modern-js/server-runtime';
+import type { RequestOption } from '@modern-js/plugin-bff/server';
 
 type IQuery = {
   // some types

package/docs/zh/guides/advanced-features/international/_meta.json

@@ -1,5 +1,4 @@
 [
-  "basic",
   "quick-start",
   "configuration",
   "locale-detection",