@modern-js/main-doc 2.59.0 → 2.60.1-alpha.0

package/docs/zh/{guides/topic-detail/framework-plugin → plugin/plugin-system}/plugin-api.mdx

@@ -44,7 +44,7 @@ interface UserConfig {
 具体配置字段的意义请参考 [配置](/configure/app/usage)。
 
 :::tip
-该方法获取到的是只读配置，不可修改。如果需要修改配置，请使用 [config hook](/guides/topic-detail/framework-plugin/hook-list.html#config)。
+该方法获取到的是只读配置，不可修改。如果需要修改配置，请使用 [config hook](/plugin/plugin-system/hook-list.html#config)。
 :::
 
 ### useResolvedConfigContext
@@ -67,7 +67,7 @@ interface NormalizedConfig {
 配置字段的完整内容请参考 [配置](/configure/app/usage)。
 
 :::tip
-该方法获取到的是只读配置，不可修改。如果需要修改配置，请使用 [config hook](/guides/topic-detail/framework-plugin/hook-list.html#config)。
+该方法获取到的是只读配置，不可修改。如果需要修改配置，请使用 [config hook](/plugin/plugin-system/hook-list.html#config)。
 :::
 
 ### useAppContext

package/docs/zh/plugin/rsbuild-plugins/_meta.json

@@ -0,0 +1 @@
+["plugin-esbuild"]

package/docs/zh/{guides → plugin}/rsbuild-plugins/plugin-esbuild.mdx

@@ -11,7 +11,7 @@ sidebar_position: 3
 
 :::
 
-import Esbuild from '@modern-js/builder-doc/docs/zh/shared/esbuild.md';
+import Esbuild from '@site-docs/components/esbuild.mdx';
 
 <Esbuild />
 
@@ -19,7 +19,7 @@ import Esbuild from '@modern-js/builder-doc/docs/zh/shared/esbuild.md';
 
 ### 在 Modern.js 框架中使用
 
-Modern.js 框架默认集成了 Builder 的 esbuild 插件，因此，你不需要手动安装和注册插件，只需要使用 [tools.esbuild](/configure/app/tools/esbuild.html) 配置项即可：
+Modern.js 框架默认集成了 esbuild 插件，因此，你不需要手动安装和注册插件，只需要使用 [tools.esbuild](/configure/app/tools/esbuild.html) 配置项即可：
 
 ```js
 export default defineConfig({
@@ -102,7 +102,7 @@ builderPluginEsbuild({
 
 #### 关闭代码转译
 
-将 `loader` 设置为 `false` 来关闭 esbuild 代码转译，此时 Builder 会继续使用 Babel 来进行代码转译。
+将 `loader` 设置为 `false` 来关闭 esbuild 代码转译，此时 Modern.js 会继续使用 Babel 来进行代码转译。
 
 ```ts
 builderPluginEsbuild({
@@ -146,7 +146,7 @@ builderPluginEsbuild({
 
 #### 关闭代码压缩
 
-将 `minimize` 设置为 `false` 来关闭 esbuild 代码压缩，此时 Builder 会继续使用 Terser 进行代码压缩。
+将 `minimize` 设置为 `false` 来关闭 esbuild 代码压缩，此时 Modern.js 会继续使用 Terser 进行代码压缩。
 
 ```ts
 builderPluginEsbuild({
@@ -156,7 +156,7 @@ builderPluginEsbuild({
 
 ## esbuild 局限性
 
-虽然 esbuild 能给现有的 webpack 项目带来明显的构建性能提升，但这个工具在接入 Builder 时还存在一定的局限性，需要大家在接入的时候格外注意。
+虽然 esbuild 能给现有的 webpack 项目带来明显的构建性能提升，但这个工具在接入 Modern.js 时还存在一定的局限性，需要大家在接入的时候格外注意。
 
 ### 兼容性
 
@@ -190,7 +190,7 @@ builderPluginEsbuild({
 
 ### 不支持 Babel 插件
 
-使用 esbuild 进行代码转译时，诸如 `babel-plugin-import` 等原有 Babel 插件的语法编译功能在开启 esbuild 后无法使用。并且由于 Builder 底层使用的是 esbuild 的 `Transform API`，因此不支持使用额外 esbuild 插件来进行自定义编译过程。
+使用 esbuild 进行代码转译时，诸如 `babel-plugin-import` 等原有 Babel 插件的语法编译功能在开启 esbuild 后无法使用。并且由于 Modern.js 底层使用的是 esbuild 的 `Transform API`，因此不支持使用额外 esbuild 插件来进行自定义编译过程。
 
 如果你有 `babel-plugin-import` 等 Babel 插件相关诉求，可以使用 SWC 插件。
 

package/docs/zh/plugin/rsbuild-plugins.mdx

@@ -0,0 +1,4 @@
+# 概览
+
+- [@modern-js/plugin-esbuild](/plugin/rsbuild-plugins/plugin-esbuild)：提供 esbuild 编译支持。
+

package/i18n.json

@@ -11,6 +11,10 @@
     "zh": "配置",
     "en": "Config"
   },
+  "plugin-menu": {
+    "zh": "插件",
+    "en": "Plugin"
+  },
   "apis": {
     "zh": "API",
     "en": "API"
@@ -71,13 +75,33 @@
     "zh": "使用 BFF",
     "en": "Using BFF"
   },
+  "page-performance": {
+    "zh": "优化页面性能",
+    "en": "Optimize Page Performance"
+  },
   "micro-frontend": {
     "zh": "微前端",
     "en": "Micro Frontend"
   },
-  "framework-plugin": {
-    "zh": "框架插件",
-    "en": "Framework Plugin"
+  "plugin-system": {
+    "zh": "插件系统",
+    "en": "Plugin System"
+  },
+  "cli-plugins": {
+    "zh": "CLI 插件",
+    "en": "CLI Plugins"
+  },
+  "server-plugins": {
+    "zh": "服务端插件",
+    "en": "Server Plugins"
+  },
+  "runtime-plugins": {
+    "zh": "运行时插件",
+    "en": "Runtime Plugins"
+  },
+  "rsbuild-plugins": {
+    "zh": "Rsbuild 插件",
+    "en": "Rsbuild Plugins"
   },
   "reduck": {
     "zh": "Reduck 状态管理",

package/package.json

@@ -15,20 +15,16 @@
     "modern",
     "modern.js"
   ],
-  "version": "2.59.0",
+  "version": "2.60.1-alpha.0",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
-    "access": "public",
-    "provenance": true
+    "access": "public"
   },
   "dependencies": {
-    "@modern-js/sandpack-react": "2.59.0"
-  },
-  "peerDependencies": {
-    "@modern-js/builder-doc": "^2.59.0"
+    "@modern-js/sandpack-react": "2.60.0"
   },
   "devDependencies": {
-    "@rspress/shared": "1.28.2",
+    "@rspress/shared": "1.31.0",
     "@types/fs-extra": "9.0.13",
     "@types/node": "^16",
     "classnames": "^2",
@@ -36,15 +32,14 @@
     "fs-extra": "^10",
     "react": "^18",
     "react-dom": "^18",
-    "rspress": "1.28.2",
+    "rspress": "1.31.0",
     "ts-node": "^10.9.1",
-    "typescript": "^5",
-    "@modern-js/builder-doc": "2.59.0"
+    "typescript": "^5"
   },
   "scripts": {
     "dev": "rspress dev",
-    "build": "npx ts-node ./scripts/sync.ts",
-    "build:doc": "rspress build",
+    "dev:no_lazy": "LAZY=false rspress dev",
+    "build": "rspress build",
     "preview": "rspress preview"
   }
 }

package/rspress.config.ts

@@ -6,61 +6,6 @@ const { version } = require('./package.json');
 
 const docPath = path.join(__dirname, 'docs');
 
-const getNavbar = (lang: string): NavItem[] => {
-  const cn = lang === 'zh';
-  const prefix = cn ? '' : '/en';
-  const getLink = (str: string) => `${prefix}${str}`;
-  const getText = (cnText: string, enText: string) => (cn ? cnText : enText);
-  return [
-    {
-      text: getText('指南', 'Guide'),
-      link: getLink('/guides/get-started/introduction'),
-      activeMatch: '/guides/',
-    },
-    {
-      text: getText('教程', 'Tutorials'),
-      link: getLink('/tutorials/foundations/introduction'),
-      activeMatch: '/tutorials/',
-    },
-    {
-      text: getText('配置', 'Configure'),
-      link: getLink('/configure/app/usage'),
-      activeMatch: '/configure/app',
-    },
-    {
-      text: getText('API', 'API'),
-      link: getLink('/apis/app/commands'),
-      activeMatch: '/apis/',
-    },
-    {
-      text: getText('社区', 'Community'),
-      link: getLink('/community/showcase'),
-      activeMatch: '/community/',
-    },
-    {
-      text: `v${version}`,
-      items: [
-        {
-          text: 'Rsbuild',
-          link: 'https://github.com/web-infra-dev/rsbuild',
-        },
-        {
-          text: 'Rspress',
-          link: 'https://github.com/web-infra-dev/rspress',
-        },
-        {
-          text: 'Modern.js Module',
-          link: 'https://modernjs.dev/module-tools/en/',
-        },
-        {
-          text: 'Modern.js v1',
-          link: 'https://modernjs.dev/v1/',
-        },
-      ],
-    },
-  ];
-};
-
 export default defineConfig({
   root: docPath,
   base: '/',
@@ -134,12 +79,10 @@ export default defineConfig({
   ],
   builderConfig: {
     output: {
-      disableTsChecker: true,
-      svgDefaultExport: 'component',
       dataUriLimit: 0,
     },
     dev: {
-      startUrl: false,
+      lazyCompilation: process.env.LAZY !== 'false',
     },
     source: {
       alias: {

package/src/components/Footer/index.tsx

@@ -76,7 +76,7 @@ export default function Footer() {
         },
         {
           label: t('pluginSystem'),
-          to: useUrl('/guides/topic-detail/framework-plugin/introduction'),
+          to: useUrl('/plugin/plugin-system/introduction'),
         },
         {
           label: t('projectGenerator'),

package/src/components/RsbuildLink/index.tsx

@@ -0,0 +1,19 @@
+import React from 'react';
+import { useLang } from 'rspress/runtime';
+
+const RsbuildLInk = ({ configName }: { configName: string }) => {
+  const lang = useLang();
+  const href = `https://rsbuild.dev/${lang === 'zh' ? 'zh/' : ''}config/${configName
+    .split('.')
+    .join('/')
+    .replace(/([a-z])([A-Z])/g, '$1-$2')
+    .toLowerCase()}`;
+
+  return (
+    <a href={href} target="__blank">
+      Rsbuild - {configName}
+    </a>
+  );
+};
+
+export default RsbuildLInk;

package/src/pages/index.tsx

@@ -1,4 +1,3 @@
-/* eslint-disable react/no-unescaped-entities */
 import clsx from 'clsx';
 import { useEffect } from 'react';
 import { Helmet, useLang, useLocation } from 'rspress/runtime';

package/docs/en/apis/app/hooks/api/api.mdx

@@ -1,80 +0,0 @@
----
-title: '**/*.[tj]s'
-sidebar_position: 1
----
-# **/*.[tj]s
-
-Files that declare API routes in the [BFF Function Mode](/guides/advanced-features/bff/type.html#function-mode). Except for some [convention files](/apis/app/hooks/api/api#allow-list), files in the `api` directory will be registered as the routes.
-
-:::info
-Using the `api` directory requires enabling the BFF feature, and you need to run the `new` command in the project to enable the "BFF" feature.
-
-This file supports using the `js` or `ts` language, but you must use `esm` syntax to export functions.
-
-:::
-
-## Routing File Convention
-
-### Default Routing
-
-The routing system will map files named `index` to the previous directory.
-
-- `api/index.ts` -> `$BASENAME/`
-- `api/user/index.ts` -> `$BASENAME/user`
-
-### Nested Routing
-
-The routing system also supports parsing nested files. If you create a nested folder structure, the files will still automatically resolve routes in the same way.
-
-- `api/hello.ts` -> `$BASENAME/hello`
-- `api/user/list.ts` -> `$BASENAME/user/list`
-
-### Dynamic Routing
-
-The routing system supports generating dynamic routes through file directories named with `[]`.
-
-- `api/user/[username]/info.ts` -> `$BASENAME/user/:username/info`
-- `api/user/[username]/delete.ts` -> `$BASENAME/user/:username/delete`
-- `api/article/[id]/info.ts` -> `$BASENAME/article/:id/info`
-
-The `$BASENAME` can be configured in `modern.config.js`, and the default value is `/api`.
-
-### Allow List
-
-By default, all files in the `api` directory will be parsed as BFF function files, but we also set a white list for these files that are not parsed:
-
-- Files whose names start with `_`. For example: `_utils.ts`.
-- All files in folders whose names start with `_`. For example: `_utils/index.ts`, `_utils/cp.ts`.
-- Test files. For example: `foo.test.ts`.
-- TypeScript type files. For example: `hello.d.ts`.
-- Files under `node_modules`.
-
-## Function Definition
-
-In addition to the routing rules above, there are also conventions for function definitions and exports in the code.
-
-Functions are exported by name, and the name of the exported function is the HTTP method accepted by the corresponding interface, that is:
-
-```ts
-export const get = async () => {
-  return {
-    name: 'Modern.js',
-    desc: 'Modern web Solutions',
-  };
-};
-```
-
-By exporting functions in this way, you will get a `GET` interface.
-
-The application project supports 9 Method definitions, namely: `GET`, `POST`, `PUT`, `DELETE`, `CONNECT`, `TRACE`, `PATCH`, `OPTION`, `HEAD`, that is, these Methods can be used as the names of the exported functions.
-
-The name is case-insensitive, that is, if it is `GET`, it can be written as `get`, `Get`, `GEt`, `GET`, all of which can be accurately recognized. The default export, that is, `export default xxx`, will be mapped to `Get`.
-
-Because `delete` is a keyword in JavaScript, you can use `del` or `DELETE` instead.
-
-Multiple functions with different Methods can be defined in one file, but if multiple functions with the same Method are defined, only the first one will take effect.
-
-:::info
-It should be noted that the defined functions should all be asynchronous, which is related to the type when calling the function.
-
-:::

package/docs/en/apis/app/hooks/api/app.mdx

@@ -1,12 +0,0 @@
----
-title: _app.[tj]s
-sidebar_position: 2
----
-# _app.[tj]s
-
-In the [BFF Function Mode](/guides/advanced-features/bff/type.html#function-mode), this file can add pre-middleware for BFF functions.
-
-:::note
-For specific examples, please refer to [hook](/apis/app/runtime/bff/hook).
-
-:::

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

@@ -1,46 +0,0 @@
----
-sidebar_position: 2
-title: BFF Type
----
-# BFF Type
-
-Runtime framework support is also an important part of **BFF**. Modern.js supports extending BFF's runtime framework through plugins, and provides a series of built-in plugins, developers can directly use the conventions and ecology of the framework.
-
-The plugin is compatible with most of the specifications of these frameworks, and each framework needs to provide two types of ways to extend the writing of BFF functions, namely **Function Mode** and **Framework Mode**.
-
-:::note
-Whether the current `api/` directory structure is written as a framework is determined by the corresponding plugin, Modern.js don't care.
-
-:::
-
-## Function Mode
-
-When the plugin considers that it is currently written as a function, it must support writing middleware in the `api/_ app.ts` to extend the BFF function.
-
-Modern.js collects the middleware in the `api/_app.ts` and passes it to the plugin, which injects the middleware into the runtime, for example:
-
-```ts
-import { hook } from '@modern-js/runtime/server';
-
-export default hook(({ addMiddleware }) => {
-  addMiddleware(myMiddleware);
-});
-```
-
-:::note
-The writing of middleware for different plugins is not the same, see [Runtime Framework](/guides/advanced-features/bff/frameworks) for details.
-
-:::
-
-## Framework Mode
-
-Framework writing is a way of using frame structure to extend BFF functions. Compared with function writing, although frame writing can use more frame structure and make the entire BFF Server clearer in complex scenarios, it is also more complex and requires more attention to the content at the framework level.
-
-In the framework writing method, all BFF functions need to be written in the `api/lambda/` directory, and the hook file `_app.[tj]s` cannot be used.
-
-In most cases, the function writing method can cover the customization requirements of most BFF functions. Only when your project server level logic is more complex, the code needs to be layered, or you need to use more elements of the framework, you need to use the framework writing method.
-
-:::note
-The directory structure of different plugin frameworks is not the same, see [Runtime Frameworks](/guides/advanced-features/bff/frameworks) for details.
-
-:::

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

@@ -1,148 +0,0 @@
----
-sidebar_position: 8
----
-
-# ESLint Rules
-
-**Modern.js ESLint Rules** is the full set of **ESLint** rules, includes `@modern-js` (Lint rules for Node.js projects) and `@modern-js-app` (Lint rules for web projects).
-
-More ESLint usage is described below with specific questions.
-
-## Q: How To Deal With Lint
-
-### Automatic Fix
-
-Most problems will be solved by the automatic fix of ESLint rules or the code formatting of [Prettier](https://prettier.io/) (which has been integrated into ESLint), and the developer does not need to care about the details of the problem and how to solve it.
-
-:::info
-This kind of automatic fix is mainly performed when the IDE saves the file, and a few will be automatically fix on submit.
-:::
-
-### Batch Automatic Fix
-
-In rare cases, such as when an old project is migrated, the following commands can be executed to repair and inspect all files in bulk:
-
-```bash
-pnpm run lint:error
-```
-
-### Manual Fix
-
-For problems that cannot be automatically fixed, you can click the rule link in the problem prompt box in the IDE to open the document of this rule to view the explanation and solution of the problem.
-
-### Claim Exceptions
-
-At this stage, some rules are not smart enough, and in most cases there will be great benefits, and in a few cases it may not apply. But if the entire rule is turned off or changed for these few cases, the gain is not worth the loss.
-
-In this case, you can use the [eslint-disable](https://eslint.org/docs/user-guide/configuring/rules#disabling-rules) comment to mark the code blocks that meet the **rare case**, stating that this is an exception and should be ignored. For example:
-
-```js
-/* eslint-disable filenames/match-exported */
-...
-/* eslint-enable filenames/match-exported */
-```
-
-:::info
-Enter eslint in the VS Code editor, a prompt box about `eslint-disable` will automatically appear, select the prompt option to generate the corresponding comment pair.
-:::
-
-[Modern.js ESLint Rule Set] requires that [eslint-disable](https://eslint.org/docs/user-guide/configuring/rules#disabling-rules) must be used in pairs, the scope to be affected must be clearly expressed, and what rules to disable within this scope must be clearly expressed, the purpose is to make **exceptions** Clear, minimized scope to avoid abuse of [eslint-disable](https://eslint.org/docs/user-guide/configuring/rules#disabling-rules), resulting in code that does not belong to the exception being disabled by the rule.
-
-## Q: How to customize ESLint rules
-
-### The `eslintConfig` field in `package.json` in the root directory
-
-This place is the default ESLint configuration for the entire repository and is designed for pure Node.js code (which can only run in Node.js).
-
-If the project does have special requirements or inevitable compatibility issues with some rules (not exceptions), you can add rule configuration here. This configuration will take precedence over the default [Modern.js ESLint ruleset], such as:
-
-
-```json
- "eslintConfig": {
-    "extends": [
-      "@modern-js"
-    ],
-    "rules": {
-      "filenames/match-exported": "off"
-    }
-  },
-
-```
-
-### `src/.eslintrc.js`
-
-Modern.js Framework or Modern.js Module project will have this configuration file by default in the source code directory, which is designed for Universal JS code.
-
-:::info
-Universal JS code is code that can run on both the browser side and the server side.
-:::
-
-If the project does have special requirements or inevitable compatibility issues with some rules (not exceptions), you can add a rule configuration here, which will take precedence over the default [Modern.js ESLint ruleset], such as:
-
-```js
-// eslint-disable-next-line import/no-commonjs
-module.exports = {
-  root: true,
-  extends: ['@modern-js-app'],
-  parserOptions: {
-    tsconfigRootDir: __dirname,
-    project: ['../tsconfig.json'],
-  },
-  rules: {
-    'filenames/match-exported': 'off',
-  },
-};
-```
-
-If necessary, you can continue to add the `.eslintrc.js` file in different subdirectories, and make special configuration for the code in this subdirectory:
-
-```js
-module.exports = {
-  rules: {
-    'filenames/match-exported': 'off',
-  },
-};
-```
-
-:::tip
-Note: It is not necessary to use the `extends` field, it will automatically inherit the configuration of the parent directory.
-
-:::
-
-### `eslintIgnore` field in `package.json`
-
-Adding directories that contain `.js`, `.jsx`, `.ts`, `.tsx` files, but do not require code inspection and automatic repair, to `eslintIgnore` can optimize the speed of ESLint inspection, such as:
-
-```json
- "eslintIgnore": [
-    "node_modules",
-    "dist",
-    "output"
-  ],
-```
-
-## Q: How to upgrade the version of the ESLint plugin
-
-As long as it is not a change in the Major version (the "^" symbol that does not comply with the [Semver](https://semver.org/) rule), you can specify this dependency directly in the `package.json` of the business project, delete the Lock file (or try to manually delete the Lock file). the contents of this package name in the file), execute `pnpm install` to reinstall the dependency and generate a new Lock file.
-
-After doing this, the plugin should only exist in the `./node_modules` directory of the business project and be upgraded to the version you specified.
-
-:::tip
-- Major version is the major version number. For more information, please read [[Semantic Versioning](https://semver.org/#summary) ].
-- All upstream projects encapsulated by Modern.js (such as ESLint, [ESLint plugin](https://eslint.org/docs/user-guide/configuring/plugins#plugins), [React Router](https://reactrouter.com/), etc.) can also be upgraded in this way.
-- Modern.js will also try to upgrade these upstream dependencies as timely as possible in each release.
-- Major version upgrades need to be published by Modern.js.
-
-:::
-
-## Q: WebStorm sometimes reports ESLint errors
-
-Since WebStorm believes that the ESLint execution directory is determined based on the `.eslintrc'` file. Therefore, the placement of the `src/.eslintrc` file location will cause the location specified by the `tsconfig.json` file (in the project root directory) to not be found in the'src/'directory.
-
-you need to configure it manually:
-
-```json
---parser-options=project:../tsconfig.json
-```
-
-![webstorm-lint-error](https://lf3-static.bytednsdoc.com/obj/eden-cn/aphqeh7uhohpquloj/modern-js/docs/webstorm-lint-error.png)

package/docs/zh/apis/app/hooks/api/api.mdx

@@ -1,81 +0,0 @@
----
-title: '**/*.[tj]s'
-sidebar_position: 1
----
-
-# **/*.[tj]s
-
-在 [BFF 函数写法](/guides/advanced-features/bff/type.html#函数写法)下，声明 API 路由的文件。除了[某些约定文件](/apis/app/hooks/api/api#白名单)外，`api` 目录下的文件会被注册为接口的路由。
-
-:::info
-使用 `api` 目录需要开启 BFF 功能，需要在项目下执行 new 命令启用「BFF」功能。
-
-该文件支持使用 `js` 或 `ts` 语言，但必须使用 `esm` 语法导出函数。
-
-:::
-
-## 该文件约定路由如下：
-
-### 默认路由
-
-路由系统会将以 `index` 命名的文件会被映射到上一层目录。
-
-- `api/index.ts` -> `$BASENAME/`
-- `api/user/index.ts` -> `$BASENAME/user`
-
-### 嵌套路由
-
-路由系统也支持解析嵌套的文件，如果创建嵌套文件夹结构，文件仍会以相同方式自动解析路由。
-
-- `api/hello.ts` -> `$BASENAME/hello`
-- `api/user/list.ts` -> `$BASENAME/user/list`
-
-### 动态路由
-
-路由系统支持通过 `[]` 命名的文件目录生成动态路由。
-
-- `api/user/[username]/info.ts` -> `$BASENAME/user/:username/info`
-- `api/user/[username]/delete.ts` -> `$BASENAME/user/:username/delete`
-- `api/article/[id]/info.ts` -> `$BASENAME/article/:id/info`
-
-其中的 `$BASENAME` 可以在 `modern.config.js` 中进行配置，默认值为 `/api`。
-
-### 白名单
-
-默认 `api` 目录下所有文件都会当作 BFF 函数文件去解析，但同样我们也设置了白名单，这些文件不被被解析：
-
-- 命名以 `_` 开头的文件。例如：`_utils.ts`。
-- 命名以 `_` 开头的文件夹下所有文件。例如：`_utils/index.ts`、`_utils/cp.ts`。
-- 测试文件。例如：`foo.test.ts`。
-- TypeScript 类型文件。例如：`hello.d.ts`。
-- `node_module` 下的文件。
-
-## 函数定义
-
-除了上面的路由规则之外，代码中函数定义与导出也有相应的约定。
-
-函数通过具名导出，导出函数的名字为对应接口接受的 HTTP Method，即：
-
-```ts
-export const get = async () => {
-  return {
-    name: 'Modern.js',
-    desc: '现代 web 工程方案',
-  };
-};
-```
-
-这样导出函数，则会得到一个 `GET` 接口。
-
-Modern.js 工程中支持了 9 个 Method 定义，即：`GET`、`POST`、`PUT`、`DELETE`、`CONNECT`、`TRACE`、`PATCH`、`OPTION`、`HEAD`，即可以用这些 Method 作为函数导出的名字。
-
-名字是大小不敏感的，就是说，如果是 `GET`，写成 `get`、`Get`、`GEt`、`GET`，都可以准确识别。而默认导出，即 `export default xxx` 则会被映射为 `Get`。
-
-因为 `delete` 是 JavaScript 中的关键字，可以使用 `del` 或者 `DELETE` 代替。
-
-可以在一个文件中定义多个不同 Method 的函数，但如果定义多个相同 Method 的函数，则只有第一个会生效。
-
-:::info
-需要注意的是，定义的函数都应该是异步的，这个与函数调用时类型有关。
-
-:::

package/docs/zh/apis/app/hooks/api/app.mdx

@@ -1,12 +0,0 @@
----
-title: _app.[tj]s
-sidebar_position: 2
----
-# _app.[tj]s
-
-在 [BFF 函数写法](/guides/advanced-features/bff/type.html#函数写法)下，该文件可以为 BFF 函数添加前置中间件。
-
-:::note
-具体示例请参考 [hook](/apis/app/runtime/bff/hook)
-
-:::