@modern-js/main-doc 3.0.0-alpha.0 → 3.0.0-alpha.1

package/docs/en/configure/app/source/include.mdx

@@ -9,10 +9,7 @@ title: include
 
 ```ts
 const defaultInclude = [
-  [
-    { not: /[\\/]node_modules[\\/]/ },
-    /\.(?:ts|tsx|jsx|mts|cts)$/,
-  ],
+  [{ not: /[\\/]node_modules[\\/]/ }, /\.(?:ts|tsx|jsx|mts|cts)$/],
 ];
 ```
 
@@ -28,10 +25,7 @@ Before Rsbuild version 1.4, the default value of `source.include` was:
 const defaultInclude = [
   [
     {
-      and: [
-        APP_ROOT,
-        { not: /[\\/]node_modules[\\/]/ }
-      ]
+      and: [APP_ROOT, { not: /[\\/]node_modules[\\/]/ }],
     },
     /\.(?:ts|tsx|jsx|mts|cts)$/,
   ],
@@ -41,12 +35,6 @@ const defaultInclude = [
 The difference from the new version is that `.js`, `.mjs`, `.cjs` files only in the current directory will be compiled.
 :::
 
-## Rspack
-
 import RsbuildConfig from '@site-docs/components/rsbuild-config-tooltip';
 
 <RsbuildConfig configName="source.include" />
-
-## Webpack
-
-To ensure legacy projects can run properly, when using Webpack, the default value of `source.include` is the same as before Rsbuild version 1.4.

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

@@ -151,16 +151,16 @@ type ProxyOptions =
   | ProxyDetail;
 ```
 
-In addition to the http-proxy-middleware option, we also support the bypass and context configuration:
+In addition to the http-proxy-middleware options, two configuration items are also supported: bypass and context:
 
-- bypass: bypass the proxy based on the return value of a function.
-  - Return `null` or `undefined` to continue processing the request with proxy.
-  - Return `false` to produce a 404 error for the request.
-  - Return a path to serve from, instead of continuing to proxy the request.
-- context: If you want to proxy multiple, specific paths to the same target, you can use an array of one or more objects with a context property.
+- bypass: Bypass the proxy based on the return value of the function.
+  - Returning `null` or `undefined` will continue to process the request with proxy.
+  - Returning `false` will return a 404 error.
+  - Returning a specific service path will use this path to replace the original request path.
+- context: If you want to proxy multiple specific paths to the same target, you can use the context configuration item.
 
 ```js
-// custom bypass
+// Custom bypass method
 export default {
   tools: {
     devServer: {
@@ -181,7 +181,7 @@ export default {
 ```
 
 ```js
-// proxy multiple
+// Proxy multiple paths to the same target
 export default {
   tools: {
     devServer: {

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

@@ -246,18 +246,6 @@ Modern.js exports the `AppUserConfig` type, which corresponds to the type of the
 ```ts title="modern.config.ts"
 import type { AppUserConfig } from '@modern-js/app-tools';
 
-const config: AppUserConfig = {
-  tools: {
-    webpack: {},
-  },
-};
-```
-
-When using Rspack as the bundler, due to some differences in configuration types between webpack and Rspack, you need to specify the ``generic for`AppUserConfig`:
-
-```ts title="modern.config.ts"
-import type { AppUserConfig } from '@modern-js/app-tools';
-
 const config: AppUserConfig = {
   tools: {
     rspack: {},

package/docs/en/guides/_meta.json

@@ -28,5 +28,10 @@
     "type": "dir",
     "name": "troubleshooting",
     "label": "troubleshooting"
+  },
+  {
+    "type": "dir",
+    "name": "upgrade",
+    "label": "Upgrade"
   }
 ]

package/docs/en/guides/advanced-features/bff/_meta.json

@@ -1 +1,9 @@
-["function", "frameworks", "extend-server", "sdk", "upload", "cross-project"]
+[
+  "function",
+  "frameworks",
+  "operators",
+  "extend-server",
+  "sdk",
+  "upload",
+  "cross-project"
+]

package/docs/en/guides/advanced-features/bff/cross-project.mdx

@@ -7,7 +7,7 @@ Cross-project invocation consists of **producer** and **consumer** sides. The pr
 
 ## BFF Producer
 
-Upgrade Modern.js dependencies to version x.64.4 or higher, then enable cross-project invocation via configuration. Projects with BFF capabilities enabled can act as BFF producers, or you can create standalone BFF applications.
+Enable cross-project invocation via configuration. Projects with BFF capabilities enabled can act as BFF producers, or you can create standalone BFF applications.
 When executing `dev` or `build`, the following artifacts for consumers will be automatically generated:
 - API functions under the `dist/client` directory
 - Runtime configuration functions under the `dist/runtime` directory

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

@@ -7,19 +7,6 @@ title: Runtime Framework
 
 Modern.js uses [Hono.js](https://hono.dev/) as the BFF and Server runtime framework, so you can [extend BFF Server](/guides/advanced-features/bff/extend-server.html) based on the Hono.js ecosystem.
 
-## Getting Request Context
+import Hono from '@site-docs-en/components/hono';
 
-Sometimes in BFF functions, it's necessary to obtain the request context to handle more logic. In such cases, you can use `useHonoContext` to get it:
-
-```ts title="api/lambda/hello.ts"
-import { useHonoContext } from '@modern-js/plugin-bff/server'
-export const get = async () => {
-  const c = useHonoContext();
-  console.info(`access url: ${c.req.url}`);
-  return 'Hello Modern.js'
-};
-```
-
-:::info
-For more details, refer to [useHonoContext](/apis/app/runtime/bff/use-hono-context).
-:::
+<Hono />

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

@@ -6,9 +6,9 @@ This invocation method is called **unified invocation**, where developers do not
 
 ## Enable BFF
 
-import EnableBFF from "@site-docs-en/components/enable-bff"
+import EnableBFF from '@site-docs-en/components/enable-bff';
 
-<EnableBFF/>
+<EnableBFF />
 
 ## BFF Functions
 
@@ -252,9 +252,9 @@ export default () => {
 
 ## Extend BFF Function
 
-import ExtendBFF from "@site-docs-en/components/extend-bff-function"
+import ExtendBFF from '@site-docs-en/components/extend-bff-function';
 
-<ExtendBFF/>
+<ExtendBFF />
 
 ## Code Sharing