@modern-js/main-doc 2.25.1 → 2.25.2

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @modern-js/main-doc
 
+## 2.25.2
+
+### Patch Changes
+
+- 4a83fcd: docs(main-doc): fix wrong links and add missing files
+  docs(main-doc): 修复错误的链接，补充缺失的文件
+  - @modern-js/builder-doc@2.25.2
+
 ## 2.25.1
 
 ### Patch Changes

package/docs/en/apis/app/commands.mdx

@@ -71,7 +71,7 @@ modern dev --entry foo,bar
 
 ## modern build
 
-The `modern build` command will build a production-ready product in the `dist/` directory by default. You can specify the output directory by modifying the configuration [`output.distPath`](/configure/app/output/dist-path).
+The `modern build` command will build production-ready artifacts in the `dist/` directory by default. You can specify the output directory by modifying the configuration [`output.distPath`](/configure/app/output/dist-path).
 
 ```bash
 Usage: modern build [options]
@@ -96,7 +96,7 @@ File sizes after production build:
   645 B      dist/static/css/main.0dd3ecc1.css
 ```
 
-Open the above HTML file in the browser, you can see the tile diagram of the packaged product, and perform package volume analysis and optimization:
+Open the above HTML file in the browser, you can see the tile diagram of the bundled files, and perform package volume analysis and optimization:
 
 <img src="https://lf3-static.bytednsdoc.com/obj/eden-cn/aphqeh7uhohpquloj/modern-js/mwa-build-analyze-8784f762c1ab0cb20935829d5f912c4c.png" />
 

package/docs/en/apis/app/hooks/config/icon.mdx

@@ -7,7 +7,7 @@ sidebar_position: 2
 
 ## Favicon
 
-When there is a `favicon.*` file in the `config` directory at the root of the project, Modern.js will automatically set the file to the [html.favicon](/configure/app/html/favicon) configuration item for generating the favicon icon on the page:
+When there is a `favicon.*` file in the `config` directory at the root of the project, Modern.js will automatically set the file to the [html.favicon](/configure/app/html/favicon) configuration option for generating the favicon icon on the page:
 
 ```
 ./config
@@ -32,7 +32,7 @@ When setting up the favicon, Modern.js looks for files in the following order:
 
 ## Apple Touch Icon
 
-When there is an `icon.*` file in the `config` directory at the root of the project, Modern.js will automatically set the file to the [html.appIcon](/configure/app/html/app-icon) configuration item for generating the Apple Touch Icon icon under the iOS system.
+When there is an `icon.*` file in the `config` directory at the root of the project, Modern.js will automatically set the file to the [html.appIcon](/configure/app/html/app-icon) configuration option for generating the Apple Touch Icon icon under the iOS system.
 
 ```
 ./config

package/docs/en/apis/app/runtime/web-server/middleware.mdx

@@ -123,7 +123,7 @@ export const middleware: SomeType = (ctx, next) => {
 };
 ```
 
-By default, the framework extension capability of Web Server is turned off after installing the framework extension plug-in. If you want to use the framework extension, you can turn it on through ['server.enableFrameworkExt'](/configure/app/server/enable-framework-ext.html).
+By default, the framework extension capability of Web Server is turned off after installing the framework extension plugin. If you want to use the framework extension, you can turn it on through ['server.enableFrameworkExt'](/configure/app/server/enable-framework-ext.html).
 
 
 :::info

package/docs/en/components/custom-router-micro-frontend.mdx

@@ -0,0 +1,40 @@
+```js title="src/App.tsx"
+import { useModuleApps } from '@modern-js/plugin-garfish/runtime';
+
+import { RouterProvider, Route, createBrowserRouter, createRoutesFromElements, BrowserRouter, Link, Outlet } from '@modern-js/runtime/router';
+
+const AppLayout = () => (
+  <>
+    <div><Link to={'/table'}>Loading conventional routed sub-applications</Link></div>
+    <div><Link to={'/dashboard'}>Loading Self-Controlled Routing Sub-Applications</Link></div>
+    <div><Link to={'/'}>Uninstall a sub-application</Link></div>
+    <Outlet />
+  </>
+)
+
+export default () => {
+  const { apps, MApp, Table, Dashboard } = useModuleApps();
+
+  // If you are not using the MApp component, you need to use createBrowserRouter to create the route.
+  const router = createBrowserRouter(
+    createRoutesFromElements(
+      <Route path="/" element={<AppLayout />}>
+        <Route key={'table'} path={'table/*'} element={<Table />} />
+        <Route key={'dashboard'} path={'dashboard/*'} element={<Dashboard />} />
+      </Route>
+    )
+  );
+
+  return (
+    // Approach 1: Use MApp to automatically load sub-applications based on the configured activeWhen parameter (this project is configured in modern.config.ts)
+    // <BrowserRouter>
+    //   <MApp />
+    // </BrowserRouter>
+
+    // Approach 2: Manually write Route components to load sub-applications, which is convenient for scenarios that require authentication and other pre-requisite operations
+    <>
+      <RouterProvider router={router} />
+    </>
+  );
+};
+```

package/docs/en/components/ua-polyfill.mdx

@@ -23,7 +23,7 @@ export default defineConfig({
 });
 ```
 
-After configuring `output.polyfill` as `ua` and executing `pnpm run build & & pnpm run serve` to start the server, visiting the page can see that the HTML product contains the following script:
+After configuring `output.polyfill` as `ua` and executing `pnpm run build & & pnpm run serve` to start the server, visiting the page can see that the HTML artifacts contains the following script:
 
 ```js
 <script src="/__polyfill__" crossorigin></script>

package/docs/en/configure/app/auto-load-plugin.mdx

@@ -24,7 +24,7 @@ export default defineConfig({
 
 ### Auto Registration plugin
 
-In addition to means registration, Modern.js also provides a way to automatically register plugins: set the `autoLoadPlugin` configuration item to `true`.
+In addition to means registration, Modern.js also provides a way to automatically register plugins: set the `autoLoadPlugin` configuration option to `true`.
 
 ```ts title="modern.config.ts"
 import { defineConfig } from '@modern-js/app-tools';

package/docs/en/configure/app/bff/proxy.mdx

@@ -28,13 +28,13 @@ export default defineConfig({
 
 Assuming the address of Modern.js BFF server is `localhost:8080`, all requests starting with `api` will be proxied to `https://cnodejs.org`, for example, the request to `localhost:8080/api/v1/topics` will be proxied to `https://cnodejs.org/api/v1/topics`.
 
-import BFFProxyPathRewrite from "@site-docs/components/bff-proxy-path-rewrite";
+import BFFProxyPathRewrite from "@site-docs-en/components/bff-proxy-path-rewrite";
 
 <BFFProxyPathRewrite />
 
 Unlike [dev.proxy](/configure/app/dev/proxy), the proxy here only applies to requests entering the BFF/API service; at the same time, this configuration can not only be used in the development environment, but also proxies corresponding requests in the production environment.
 
-import BFFProxyPrinciple from "@site-docs/components/bff-proxy-principle";
+import BFFProxyPrinciple from "@site-docs-en/components/bff-proxy-principle";
 
 <BFFProxyPrinciple />
 

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

@@ -53,7 +53,7 @@ export default defineConfig({
 });
 ```
 
-### Plugin configuration items
+### Plugin configuration options
 
 If the plugin provides some custom configuration options, you can pass in the configuration through the parameters of the plugin function.
 

package/docs/en/configure/app/runtime/master-app.mdx

@@ -37,4 +37,4 @@ interface AppInfo {
 
 In the `masterApp` configuration, developers can pass through options supported by Garfish
 
-All supported configuration items [see here](https://garfishjs.org/api/run/#%E5%8F%82%E6%95%B0).
+All supported configuration options [see here](https://garfishjs.org/api/run/#%E5%8F%82%E6%95%B0).

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

@@ -9,7 +9,7 @@ sidebar_label: state
 
 Once `state` is enabled, you can use [Model](/guides/topic-detail/model/quick-start) for state management.
 
-The specific configuration items are as follows:
+The specific configuration options are as follows:
 
 ## models
 

package/docs/en/guides/advanced-features/bff/index.mdx

@@ -1,6 +1,7 @@
 ---
 title: BFF
 ---
+
 # BFF
 
 In the development of the concept of **front back separation**, the front-end part can do more and more things, and the front-end needs some UI-oriented data interfaces, so the industry introduced the concept of BFF (Backends for Frontends).

package/docs/en/guides/advanced-features/code-split.mdx

@@ -16,7 +16,7 @@ When using Modern.js [Conventional routing](/guides/basic-features/routes#conven
 
 ## import
 
-use dynamic `import()`, the JS modules pass to this API will be packaged as a separate JS file, for example:
+use dynamic `import()`, the JS modules pass to this API will be bundled as a separate JS file, for example:
 
 ```ts
 import('./math').then(math => {

package/docs/en/guides/advanced-features/rspack-start.mdx

@@ -92,4 +92,4 @@ Usually it is available and any errors that arise will fixed promptly.
 However, if there are any break changes that require modern.js to modify the code, we recommend to wait for the next version of modern.js.
 :::
 
-More examples of using package management tools, please refer to: [Lock nested dependency](/guides/get-started/upgrade.html#lock-nested-dependency).
+More examples of using package managers, please refer to: [Lock nested dependency](/guides/get-started/upgrade.html#lock-nested-dependency).

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

@@ -251,7 +251,7 @@ if (process.env.MODERN_TARGET === 'browser') {
 }
 ```
 
-After the development environment is packaged, the SSR and CSR products will be compiled into the following content. Therefore, there will be no more Web API errors in the SSR environment.
+After the development environment is bundled, the SSR and CSR artifacts will be compiled into the following content. Therefore, there will be no more Web API errors in the SSR environment.
 
 ```ts
 // SSR production

package/docs/en/guides/basic-features/data-fetch.mdx

@@ -336,7 +336,7 @@ export default async (): Promise<ProfileData> => {
 };
 ```
 
-4. When running on the server, the `loader` function will be packaged into a unified bundle, so we do not recommend using `__filename` and `__dirname` in server-side code.
+4. When running on the server, the `loader` function will be bundled into a unified bundle, so we do not recommend using `__filename` and `__dirname` in server-side code.
 
 ### FAQ
 

package/docs/en/guides/topic-detail/changesets/add.mdx

@@ -19,7 +19,7 @@ A changeset includes:
 ## Steps
 
 :::info
-The following example commands are all using pnpm. If you need to use other package management tools, please replace them as needed.
+The following example commands are all using pnpm. If you need to use other package managers, please replace them as needed.
 :::
 
 ### NPM Module

package/docs/en/guides/topic-detail/changesets/release-pre.mdx

@@ -9,7 +9,7 @@ Before doing an actual release, we also need to publish a pre-release version fo
 ## Steps
 
 :::info
-The following example commands are all using pnpm. If you need to use other package management tools, please replace them as needed.
+The following example commands are all using pnpm. If you need to use other package managers, please replace them as needed.
 :::
 
 #### Run the bump command to upgrade the version of the pre-release

package/docs/en/guides/topic-detail/changesets/release.mdx

@@ -9,7 +9,7 @@ When releasing a version, we need to upgrade the version of the corresponding pa
 ## Steps
 
 :::info
-The following example commands are all using pnpm. If you need to use other package management tools, please replace them as needed.
+The following example commands are all using pnpm. If you need to use other package managers, please replace them as needed.
 
 :::
 

package/docs/en/guides/topic-detail/generator/create/option.md

@@ -65,9 +65,9 @@ By default, `@modern-js/create` will automatically identify the user's system la
 
 Specify the default project configuration.
 
-By default, `@modern-js/create` will prompt for interactive questions such as language selection and package management tools during the execution process. When it is necessary to specify these configuration contents in advance, they can be passed in through this field.
+By default, `@modern-js/create` will prompt for interactive questions such as language selection and package managers during the execution process. When it is necessary to specify these configuration contents in advance, they can be passed in through this field.
 
-This field is a JSON string. For example, when specifying a package management tool:
+This field is a JSON string. For example, when specifying a package manager:
 
 ```bash
 npx @modern-js/create@latest --config '{"packageManager": "pnpm"}'
@@ -122,7 +122,7 @@ npx @modern-js/create@next --dist-tag next
 
 Specify specific package version dependencies when creating a project.
 
-If you need to specify a specific package version when creating a project, you can use this parameter. This parameter will configure `pnpm.overrides` (if the package management tool is pnpm) or `resolutions` to lock the package version number in the `package.json` file in the project root directory.
+If you need to specify a specific package version when creating a project, you can use this parameter. This parameter will configure `pnpm.overrides` (if the package manager is pnpm) or `resolutions` to lock the package version number in the `package.json` file in the project root directory.
 
 The parameter value is a JSON string.
 

package/docs/en/guides/topic-detail/generator/plugin/api/afterForged.md

@@ -46,4 +46,4 @@ Parameters:
 
 ### install
 
-Installs dependencies in the root directory of the project. The `install` function will use the corresponding package management tool according to the value of `packageManager` to install dependencies.
+Installs dependencies in the root directory of the project. The `install` function will use the corresponding package manager according to the value of `packageManager` to install dependencies.

package/docs/en/guides/topic-detail/micro-frontend/c02-development.mdx

@@ -39,7 +39,7 @@ After the project is created, we can enable the `micro frontend` through `pnpm r
 
 Next, let's register the micro frontend plugin and add the main micro frontend app and add the list of sub-apps:
 
-import EnableMicroFrontend from "@site-docs/components/enable-micro-frontend";
+import EnableMicroFrontend from "@site-docs-en/components/enable-micro-frontend";
 
 <EnableMicroFrontend />
 
@@ -127,7 +127,7 @@ Since it is a self-controlled route, we delete the `routes/` folder and add the
 
 #### Load sub-app
 
-import CustomRouterMicroFrontend from "@site-docs/components/custom-router-micro-frontend";
+import CustomRouterMicroFrontend from "@site-docs-en/components/custom-router-micro-frontend";
 
 <CustomRouterMicroFrontend />
 

package/docs/en/guides/topic-detail/micro-frontend/c03-main-app.mdx

@@ -8,7 +8,7 @@ In the previous [Experience micro frontend](/guides/topic-detail/micro-frontend/
 
 After creating an application project through the `@modern-js/create` command, you can execute `pnpm run new` in the project (the `modern new` command is actually executed). After selecting the 「micro frontend」 mode, the micro frontend will be installed. Dependencies, just register the plugin manually.
 
-import EnableMicroFrontend from "@site-docs/components/enable-micro-frontend";
+import EnableMicroFrontend from "@site-docs-en/components/enable-micro-frontend";
 
 <EnableMicroFrontend />
 
@@ -23,10 +23,10 @@ You can register the sub-application information directly through the configurat
 :::tip
 It can be configured at runtime via the API [defineConfig](/apis/app/runtime/app/define-config).
 
-When the parameter is a function, it cannot be serialized to the product code, so please configure it through defineConfig when it comes to configuration such as functions
+When the parameter is a function, it cannot be serialized to the output code, so please configure it through defineConfig when it comes to configuration such as functions
 :::
 
-import MicroRuntimeConfig from "@site-docs/components/micro-runtime-config";
+import MicroRuntimeConfig from "@site-docs-en/components/micro-runtime-config";
 
 <MicroRuntimeConfig />
 

package/docs/en/guides/topic-detail/model/manage-effects.mdx

@@ -248,5 +248,5 @@ const handleClick = async () => {
 ```
 
 :::info
-[Example](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/effects)
+[Example](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/effects)
 :::

package/docs/en/guides/topic-detail/model/model-communicate.mdx

@@ -100,7 +100,7 @@ The final effect is as follows:
 ![communicate-models](https://lf3-static.bytednsdoc.com/obj/eden-cn/aphqeh7uhohpquloj/modern-js/docs/models-communicate.gif)
 
 :::info Additional Information
-- Full example code for this section can be found [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/models-communication).
+- Full example code for this section can be found [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/models-communication).
 - For more information about the relevant API, please refer to: [model](/apis/app/runtime/model/model_#function-types).
 
 :::

package/docs/en/guides/topic-detail/model/performance.mdx

@@ -165,6 +165,6 @@ const barModel = model("bar").define({
 We created a caching function `createSelector`, which only recalculates the value of `combineA` when the state of `barModel` changes or the state `a` of `fooModel` changes.
 
 :::info Additional Information
-You can find the complete example code of this section [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/performance-optimization).
+You can find the complete example code of this section [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/performance-optimization).
 :::
 

package/docs/en/guides/topic-detail/model/quick-start.mdx

@@ -4,7 +4,7 @@ title: Quick Start
 ---
 # Quick Start
 
-import ReduckMigration from "@site-docs/components/reduck-migration"
+import ReduckMigration from "@site-docs-en/components/reduck-migration"
 
 <ReduckMigration />
 
@@ -110,5 +110,5 @@ The final demonstration effect is as follows:
 
 ![countModel](https://lf3-static.bytednsdoc.com/obj/eden-cn/eueh7vhojuh/modern/simple-count-model.gif)
 
-That completes a simple counter application. You can view the complete example code for this section [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/counter-model).
+That completes a simple counter application. You can view the complete example code for this section [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/counter-model).
 

package/docs/en/guides/topic-detail/model/use-model.mdx

@@ -163,7 +163,7 @@ function ThreeComponent() {
 
 Using React's refs can also achieve similar effects. In fact, `useStaticModel` also uses refs internally. However, using `useStaticModel` directly helps decouple the state management logic from the component and converge it into the Model layer.
 
-The complete sample code can be found [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/static-model).
+The complete sample code can be found [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/static-model).
 
 ### Using as Local State
 
@@ -194,7 +194,7 @@ Click the `add` button of `Counter` and `LocalCounter` respectively, and the sta
 
 ![local-model](https://lf3-static.bytednsdoc.com/obj/eden-cn/eueh7vhojuh/modern/local-model.gif)
 
-The complete sample code can be found [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/local-model).
+The complete sample code can be found [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/local-model).
 
 ## Using outside of components
 
@@ -237,7 +237,7 @@ setInterval(() => {
 }, 1000);
 ```
 
-The complete sample code can be found [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/counter-model-outof-react).
+The complete sample code can be found [here](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/counter-model-outof-react).
 
 :::info
 If the Store object is manually created through [`createStore`](/apis/app/runtime/model/create-store), there is no need to obtain it through `useStore` in the component, and it can be used directly.

package/docs/zh/apis/monorepo/commands/deploy.mdx

@@ -9,7 +9,7 @@ Usage: modern deploy [options]
 deploy project
 
 Options:
-  -p, --path [path]  Specify the path of the product output (default: "output")
+  -p, --path [path]  Specify the path of the output files (default: "output")
   -h, --help         display help for command
 ```
 

package/docs/zh/guides/topic-detail/model/manage-effects.mdx

@@ -255,6 +255,6 @@ const handleClick = async () => {
 ```
 
 :::info 补充信息
-[示例代码](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/effects)
+[示例代码](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/effects)
 
 :::

package/docs/zh/guides/topic-detail/model/model-communicate.mdx

@@ -100,7 +100,7 @@ Modern.js 默认开启 [自动生成 actions](./auto-actions.mdx)，所以 `step
 ![communicate-models](https://lf3-static.bytednsdoc.com/obj/eden-cn/aphqeh7uhohpquloj/modern-js/docs/models-communicate.gif)
 
 :::info 补充信息
-- 本节完整的[示例代码](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/models-communication)。
+- 本节完整的[示例代码](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/models-communication)。
 - 相关 API 的更多介绍，请参考：[model](/apis/app/runtime/model/model_#函数类型)。
 
 :::

package/docs/zh/guides/topic-detail/model/performance.mdx

@@ -166,6 +166,6 @@ const barModel = model("bar").define({
 我们创建缓存函数 `createSelector`，仅当 `barModel` 的状态发生改变或 `fooModel` 的 `a` 状态发生改变时，才会重新计算 `combineA` 的值。
 
 :::info 补充信息
-本节完整的[示例代码](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/performance-optimization)
+本节完整的[示例代码](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/performance-optimization)
 
 :::

package/docs/zh/guides/topic-detail/model/quick-start.mdx

@@ -110,4 +110,4 @@ function Counter() {
 
 ![countModel](https://lf3-static.bytednsdoc.com/obj/eden-cn/eueh7vhojuh/modern/simple-count-model.gif)
 
-这样，我们就完了一个简单的计数器应用。本节完整的示例代码可以在[这里](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/counter-model)查看。
+这样，我们就完了一个简单的计数器应用。本节完整的示例代码可以在[这里](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/counter-model)查看。

package/docs/zh/guides/topic-detail/model/use-model.mdx

@@ -164,7 +164,7 @@ function ThreeComponent() {
 
 使用 React 的 refs 也可以实现类似效果，其实 `useStaticModel` 内部也使用到了 refs。不过直接 `useStaticModel` 有助于将状态的管理逻辑从组件中解耦，统一收敛到 Model 层。
 
-完整的示例代码可以在[这里](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/static-model)查看。
+完整的示例代码可以在[这里](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/static-model)查看。
 
 ### 作为局部状态使用
 
@@ -196,7 +196,7 @@ function LocalCounter() {
 
 ![local-model](https://lf3-static.bytednsdoc.com/obj/eden-cn/eueh7vhojuh/modern/local-model.gif)
 
-完整的示例代码可以在[这里](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/local-model)查看。
+完整的示例代码可以在[这里](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/local-model)查看。
 
 ## 在组件外使用
 
@@ -240,7 +240,7 @@ setInterval(() => {
 }, 1000);
 ```
 
-完整的示例代码可以在[这里](https://github.com/web-infra-dev/modern-js-examples/tree/main/series/tutorials/runtime-api/model/counter-model-outof-react)查看。
+完整的示例代码可以在[这里](https://github.com/web-infra-dev/modern-js-examples/tree/main/examples/runtime-api/counter-model-outof-react)查看。
 
 :::info
 如果是通过 [`createStore`](/apis/app/runtime/model/create-store) 手动创建的 Store 对象，无需通过 `useStore` 在组件内获取，即可直接使用。

package/package.json

@@ -15,14 +15,14 @@
     "modern",
     "modern.js"
   ],
-  "version": "2.25.1",
+  "version": "2.25.2",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
     "access": "public",
     "provenance": true
   },
   "peerDependencies": {
-    "@modern-js/builder-doc": "^2.25.1"
+    "@modern-js/builder-doc": "^2.25.2"
   },
   "devDependencies": {
     "classnames": "^2",
@@ -34,9 +34,9 @@
     "fs-extra": "^10",
     "@types/node": "^16",
     "@types/fs-extra": "^9",
-    "@modern-js/builder-doc": "2.25.1",
-    "@modern-js/doc-tools": "2.25.1",
-    "@modern-js/doc-plugin-auto-sidebar": "2.25.1"
+    "@modern-js/builder-doc": "2.25.2",
+    "@modern-js/doc-plugin-auto-sidebar": "2.25.2",
+    "@modern-js/doc-tools": "2.25.2"
   },
   "scripts": {
     "dev": "modern dev",

package/docs/zh/apis/monorepo/commands/_category_.json

@@ -1,8 +0,0 @@
-{
-  "label": "命令",
-  "position": 4,
-  "link": {
-    "type": "doc",
-    "id": "apis/monorepo/commands/index"
-  }
-}

package/docs/zh/apis/monorepo/commands/bump.mdx

@@ -1,39 +0,0 @@
----
-sidebar_position: 4
----
-
-```bash
-Usage: modern bump [options]
-
-使用变更集自动更新发布版本和变更日志
-
-Options:
-  --canary       创建一个预发布版本进行测试 (default: false)
-  --preid <tag>  在对预发布版本进行版本控制时指定标识符 (default: "next")
-  --snapshot     创建一个特殊版本进行测试 (default: false)
-  -h, --help     display help for command
-```
-
-:::info
-`bump` 命令执行之前需要提前执行 [`change`](/apis/monorepo/commands/change) 命令添加 changeset。
-
-:::
-
-按 changeset 记录修改 `package.json` 中的版本号， 同时生成 `CHANGELOG.md`：
-
-```bash
-npx modern bump
-🦋  All files have been updated. Review them and commit at your leisure
-```
-
-`CHANGELOG.md` 示例内容如下：
-
-```md
-# package-a
-
-## 0.1.1
-
-### Patch Changes
-
-- test publish
-```

package/docs/zh/apis/monorepo/commands/change.mdx

@@ -1,57 +0,0 @@
----
-sidebar_position: 2
----
-# change
-
-```bash
-Usage: modern change [options]
-
-创建变更集
-
-Options:
-  --empty     创建空变更集 (default: false)
-  --open      使用编辑器中打开创建的变更集 (default: false)
-  -h, --help  display help for command
-```
-
-:::info
-[`change`](/apis/monorepo/commands/change)、[`pre`](/apis/monorepo/commands/pre)、[`bump`](/apis/monorepo/commands/bump)、[`release`](/apis/monorepo/commands/release) 命令集成了工具 [`changesets`](https://github.com/atlassian/changesets) 管理版本变更和 Changelog。
-
-:::
-
-`modern change` 命令添加 changeset：
-
-```bash
-$ npx modern change
-🦋  Which packages would you like to include? · package-a, package-b
-🦋  Which packages should have a major bump? · No items were selected
-🦋  Which packages should have a minor bump? · No items were selected
-🦋  The following packages will be patch bumped:
-🦋  package-a@0.1.0
-🦋  package-b@0.1.0
-🦋  Please enter a summary for this change (this will be in the changelogs). Submit empty line to open external editor
-🦋  Summary · test publish
-🦋  === Releasing the following packages ===
-🦋  [Patch]
-🦋    package-a, package-b
-🦋  ╔════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╗
-🦋  ║                                                      ========= NOTE ========                                                       ║
-🦋  ║All dependents of these packages that will be incompatible with the new version will be patch bumped when this changeset is applied.║
-🦋  ╚════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╝
-🦋  Is this your desired changeset? (Y/n) · true
-🦋  Changeset added! - you can now commit it
-🦋
-🦋  If you want to modify or expand on the changeset summary, you can find it here
-🦋  info /xxxx/monorepo/.changeset/long-lizards-talk.md
-```
-
-上面我们给 `package-a` 和 `package-b` 都选择了 `patch` 变更，具体的变更信息在 monorepo 根目录下的 `.changeset/long-lizards-talk.md` 中:
-
-```md
----
-'package-a': patch
-'package-b': patch
----
-
-test publish
-```

package/docs/zh/apis/monorepo/commands/clear.mdx

@@ -1,24 +0,0 @@
----
-sidebar_position: 8
----
-# clear
-
-```bash
-Usage: modern clear [options]
-
-clear project dirs
-
-Options:
-  --remove-dirs [dirs...]  remove dirs, default is node_modules
-  -h, --help               display help for command
-```
-
-默认对 Monorepo 以及 Monorepo 子项目的 `node_modules` 进行清理。
-
-可以通过参数 `--remove-dirs` 来指定要删除的目录，例如执行：
-
-```bash
-$ npx modern clear --remove-dirs dist
-```
-
-则会清理所有 Monorepo 子项目的 `dist` 目录。

package/docs/zh/apis/monorepo/commands/gen-release-note.mdx

@@ -1,32 +0,0 @@
----
-sidebar_position: 9
----
-# gen-release-note
-
-```bash
-Usage: modern gen-release-note [options]
-
-根据当前仓库 changeset 文件生成 Release Note
-
-Options:
-  --repo <repo>      仓库名称，用于生成 Pull Request 链接， 例如： web-infra-dev/modern.js
-  --custom <cumtom>  自定义 Release Note 生成函数
-  -h, --help         display help for command
-```
-
-根据当前仓库的 changeset 信息自动生成 Release Note。
-
-:::warning 注意
-需要在 bump 命令之前执行。
-
-:::
-
-```markdown
-## Features:
-
-[[#1160](https://github.com/web-infra-dev/modern.js/pull/1160)] export ExecaError type
-
-## Bug Fix:
-
-[[#1264](https://github.com/web-infra-dev/modern.js/pull/1264)] fix: conventional router app use App.init not work
-```

package/docs/zh/apis/monorepo/commands/index.mdx

@@ -1,7 +0,0 @@
----
-type: ref
----
-
-# 命令
-
-本节涵盖了使用 Monorepo 工程的所有命令。

package/docs/zh/apis/monorepo/commands/lint.mdx

@@ -1,18 +0,0 @@
----
-sidebar_position: 6
----
-# lint
-
-```bash
-Usage: modern lint [options] [...files]
-
-lint and fix source files
-
-Options:
-  --no-fix    disable auto fix source file
-  -h, --help  display help for command
-```
-
-运行 `ESLint` 检查 monorepo 中代码语法情况， 通长情况下，我们只需要在 `git commit` 阶段通过 `lint-staged` 检查本次提交修改的部分代码。
-
-- `--no-fix` 参数设置后可以关闭自动修复 lint 错误代码的能力。

package/docs/zh/apis/monorepo/commands/new.mdx

@@ -1,39 +0,0 @@
----
-sidebar_position: 1
----
-# new
-
-```bash
-Usage: modern new [options]
-
-Monorepo 创建子项目
-
-Options:
-  -d, --debug            开启 Debug 模式，打印调试日志信息 (default: false)
-  -c, --config <config>  生成器运行默认配置(JSON 字符串)
-  --dist-tag <tag>       生成器使用特殊的 npm Tag 版本
-  --registry             生成器运行过程中定制 npm Registry
-  -h, --help             display help for command
-```
-
-`modern new` 命令在 monorepo 中可以用来添加应用工程和可复用的模块：
-
-```bash
-$ modern new
-? 请选择你想创建的工程类型 (Use arrow keys)
-❯ Web 应用
-  Web 应用（测试）
-  Npm 模块
-  Npm 模块（内部）
-```
-
-应用工程默认会添加到 `apps` 目录， 测试应用会添加到 `examples` 目录，公共模块默认会添加到 `packages` 目录， 内部模块默认会添加到 `features` 目录。
-
-内部模块在 monorepo 的应用里面使用时，可以无需构建直接使用源码。
-
-:::caution 注意
-`--config` 参数对应参数值需要使用 JSON 字符串。
-
-pnpm 暂不支持使用 JSON 字符串作为参数值，可使用 `npm new` 开启相关功能。【[相关 Issue](https://github.com/pnpm/pnpm/issues/3876)】
-
-:::

package/docs/zh/apis/monorepo/commands/pre.mdx

@@ -1,65 +0,0 @@
----
-sidebar_position: 3
----
-# pre
-
-```bash
-Usage: modern pre [options] <enter|exit> [tag]
-
-进入和退出预发布模式
-
-Options:
-  -h, --help  display help for command
-```
-
-可以使用 `modern pre` 命令在正式发布前[预发布](https://github.com/atlassian/changesets/blob/main/docs/prereleases.md)一个版本。
-
-首先 `modern pre enter <tag>` 进入预发布模式:
-
-```bash
-$ npx modern pre enter next
-🦋  success Entered pre mode with tag next
-🦋  info Run `changeset version` to version packages with prerelease versions
-```
-
-之后通过 `modern change` 命令添加 changeset:
-
-```bash
-$ npx modern change
-🦋  Which packages would you like to include? · package-a, package-b
-🦋  Which packages should have a major bump? · No items were selected
-🦋  Which packages should have a minor bump? · No items were selected
-🦋  The following packages will be patch bumped:
-🦋  package-a@0.1.1
-🦋  package-b@0.1.1
-🦋  Please enter a summary for this change (this will be in the changelogs). Submit empty line to open external editor
-🦋  Summary · test pre publish
-🦋  === Releasing the following packages ===
-🦋  [Patch]
-🦋    package-a, package-b
-🦋  ╔════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╗
-🦋  ║                                                      ========= NOTE ========                                                       ║
-🦋  ║All dependents of these packages that will be incompatible with the new version will be patch bumped when this changeset is applied.║
-🦋  ╚════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╝
-🦋  Is this your desired changeset? (Y/n) · true
-🦋  Changeset added! - you can now commit it
-🦋
-🦋  If you want to modify or expand on the changeset summary, you can find it here
-🦋  info /xxxxxx/monorepo/.changeset/beige-paws-rule.md
-```
-
-接着可以使用 `modern bump` 命令更新具体的版本号：
-
-```bash
-$ npx modern bump
-🦋  warn ===============================IMPORTANT!===============================
-🦋  warn You are in prerelease mode
-🦋  warn If you meant to do a normal release you should revert these changes and run `changeset pre exit`
-🦋  warn You can then run `changeset version` again to do a normal release
-🦋  warn ----------------------------------------------------------------------
-🦋  All files have been updated. Review them and commit at your leisure
-```
-
-可以看到 `package-a` 和 `package-b` 的 `package.json` 中版本号均已更新到 `0.1.2-next.0`。
-
-提交完变更之后，我们可以通过 `modern pre exit` 命令退出预发布模式。

package/docs/zh/apis/monorepo/commands/release.mdx

@@ -1,16 +0,0 @@
----
-sidebar_position: 5
----
-# release
-
-```bash
-Usage: modern release [options]
-
-publish changes to npm
-
-Options:
-  --tag <tag>  publish use special tag (default: "")
-  -h, --help   display help for command
-```
-
-发布当前仓库的 Packages 至 NPM。

package/docs/zh/apis/monorepo/commands/upgrade.mdx

@@ -1,20 +0,0 @@
----
-sidebar_position: 11
----
-# upgrade
-
-```
-Usage: modern upgrade [options]
-
-升级 Modern.js 到最新版本
-
-Options:
-  --registry <registry>  定制 npm registry (default: "")
-  -d,--debug             开启 Debug 模式，打印调试日志信息 (default: false)
-  --cwd <cwd>            项目路径 (default: "")
-  -h, --help             display help for command
-```
-
-`modern upgrade` 命令，用于升级项目 Modern.js 相关依赖至最新版本。
-
-在项目根目录下执行命令 `npx modern upgrade`，会默认将当前执行命令项目的 `package.json` 中的 Modern.js 相关依赖更新至最新版本。

package/docs/zh/apis/monorepo/hooks/_category_.json

@@ -1,8 +0,0 @@
-{
-  "label": "文件约定",
-  "position": 3,
-  "link": {
-    "type": "doc",
-    "id": "apis/monorepo/hooks/index"
-  }
-}

package/docs/zh/apis/monorepo/hooks/apps.mdx

@@ -1,14 +0,0 @@
----
-title: apps/*
-sidebar_position: 1
----
-# apps/*
-
-Monorepo 工程方案应用类型项目目录。
-
-Modern.js Monorepo 工程方案约定将应用类型子项目放置在 `apps` 目录下进行统一管理，`apps` 目录下每一个文件夹都是一个完整的应用项目。
-
-:::info
-可直接在项目下执行 new 命令创建应用类型子项目。
-
-:::

package/docs/zh/apis/monorepo/hooks/code-workspace.mdx

@@ -1,11 +0,0 @@
----
-title: monorepo.code-workspace
-sidebar_position: 7
----
-# monorepo.code-workspace
-
-Monorepo 工程方案 VS Code 配置文件。
-
-Monorepo 工程方案支持 VS Code Workspace 配置，可以通过该配置文件打开的一个或多个文件夹的集合。
-
-VS Code workspace 协议详情可查看: [VS Code Workspace](https://code.visualstudio.com/docs/editor/workspaces)

package/docs/zh/apis/monorepo/hooks/examples.mdx

@@ -1,16 +0,0 @@
----
-title: examples/*
-sidebar_position: 2
----
-# examples/*
-
-Monorepo 工程方案测试应用类型项目目录。
-
-Modern.js Monorepo 工程方案约定将测试的应用类型子项目放置在 `examples` 目录下进行统一管理，`examples` 目录下每一个文件夹都是一个完整的应用项目。
-
-测试类型的应用项目不包含部署相关的 scripts 命令，用于开发过程中进行测试项目、测试案例的编写。
-
-:::info
-可直接在项目下执行 new 命令创建测试应用类型子项目。
-
-:::

package/docs/zh/apis/monorepo/hooks/features.mdx

@@ -1,16 +0,0 @@
----
-title: features/
-sidebar_position: 3
----
-# features/
-
-Monorepo 工程方案内部模块类型项目目录。
-
-Modern.js Monorepo 工程方案约定将内部模块类型子项目放置在 `features` 目录下进行统一管理，`features` 目录下每一个文件夹都是一个完整的模块项目。
-
-内部模块项目用于一些不需要编译的公共的组件和工具的编写，这类型的项目不包含编译、发布命令，在应用类型项目中引用时，应用类型项目会默认对其进行编译。
-
-:::info
-可直接在项目下执行 new 命令内部模块类型子项目。
-
-:::

package/docs/zh/apis/monorepo/hooks/index.mdx

@@ -1,7 +0,0 @@
----
-type: ref
----
-
-# 命令
-
-本节涵盖了使用 Monorepo 工程所有的文件约定

package/docs/zh/apis/monorepo/hooks/packages.mdx

@@ -1,16 +0,0 @@
----
-title: packages/
-sidebar_position: 4
----
-# packages/
-
-Monorepo 工程方案公共模块类型项目目录。
-
-Modern.js Monorepo 工程方案约定将公共模块类型子项目放置在 `packages` 目录下进行统一管理，`packages` 目录下每一个文件夹都是一个完整的模块项目。
-
-公共模块项目用户一些公共的组件和工具的编写，这些公共包可自行进行编译和发布，也可在应用类型项目中引用。
-
-:::info
-可直接在项目下执行 new 命令创建模块类型子项目。
-
-:::

package/docs/zh/apis/monorepo/hooks/pnpm-workspace.mdx

@@ -1,11 +0,0 @@
----
-title: pnpm-workspace.yaml
-sidebar_position: 5
----
-# pnpm-workspace.yaml
-
-Monorepo 工程方案 pnpm workspace 配置文件。
-
-Monorepo 工程方案支持使用 pnpm 作为包管理工具对项目进行管理，支持 pnpm 的 workspace 协议。
-
-pnpm workspace 配置详情可查看: [pnpm workspace](https://pnpm.io/workspaces)

package/docs/zh/apis/monorepo/hooks/pnpmfile.mdx

@@ -1,11 +0,0 @@
----
-title: .pnpmfile.cjs
-sidebar_position: 6
----
-# .pnpmfile.cjs
-
-Monorepo 工程方案 pnpm 钩子文件。
-
-Monorepo 工程方案支持使用 pnpm 作为包管理工具对项目进行管理，支持使用 pnpm 的钩子文件对安装过程进行自定义。
-
-pnpm .pnpmfile.cjs 使用详情可查看: [pnpmfile](https://pnpm.io/pnpmfile)