docs(cn): update /config file

.vitepress/config.ts

@@ -262,11 +262,11 @@ export default ({ mode }: { mode: string }) => {
       sidebar: {
         '/config': [
           {
-            text: 'Config Reference',
+            text: '配置索引',
             collapsed: false,
             items: [
               {
-                text: '配置文件',
+                text: '配置 Vitest',
                 link: '/config/',
               },
               {

config/alias.md

@@ -1,18 +1,18 @@
 ---
-title: alias | Config
+title: alias | 配置
 outline: deep
 ---
 
 # alias
 
-- **Type:** `Record<string, string> | Array<{ find: string | RegExp, replacement: string, customResolver?: ResolverFunction | ResolverObject }>`
+- **类型:** `Record<string, string> | Array<{ find: string | RegExp, replacement: string, customResolver?: ResolverFunction | ResolverObject }>`
 
-Define custom aliases when running inside tests. They will be merged with aliases from `resolve.alias`.
+定义在测试运行时的自定义别名。这些别名将与 `resolve.alias` 中的配置合并使用。
 
 ::: warning
-Vitest uses Vite SSR primitives to run tests which has [certain pitfalls](https://vitejs.dev/guide/ssr.html#ssr-externals).
+Vitest 使用 Vite SSR 基元来运行测试，这有 [一定的缺陷](https://cn.vitejs.dev/guide/ssr.html#ssr-externals)。
 
-1. Aliases affect only modules imported directly with an `import` keyword by an [inlined](/config/server#server-deps-inline) module (all source code is inlined by default).
-2. Vitest does not support aliasing `require` calls.
-3. If you are aliasing an external dependency (e.g., `react` -> `preact`), you may want to alias the actual `node_modules` packages instead to make it work for externalized dependencies. Both [Yarn](https://classic.yarnpkg.com/en/docs/cli/add/#toc-yarn-add-alias) and [pnpm](https://pnpm.io/aliases/) support aliasing via the `npm:` prefix.
+1. 别名只影响由 [inlined](/config/server#server-deps-inline) 模块直接用 `import` 关键字导入的模块（默认情况下所有源代码都是内联的）。
+2. Vitest 不支持对 `require` 调用进行别名。
+3. 如果我们要别名外部依赖（例如，`react` -> `preact`），我们可能需要别名实际的 `node_modules` 包，以使其适用于外部依赖。[Yarn](https://classic.yarnpkg.com/en/docs/cli/add/#toc-yarn-add-alias) 和 [pnpm](https://pnpm.io/aliases/) 都支持通过 `npm:` 前缀进行别名。
 :::

config/allowonly.md

@@ -9,7 +9,7 @@ outline: deep
 
 - **Type**: `boolean`
 - **Default**: `!process.env.CI`
-- **CLI:** `--allowOnly`, `--allowOnly=false`
+- **命令行终端:** `--allowOnly`, `--allowOnly=false`
 
 By default, Vitest does not permit tests marked with the [`only`](/api/test#test-only) flag in Continuous Integration (CI) environments. Conversely, in local development environments, Vitest allows these tests to run.
 

config/api.md

@@ -7,16 +7,16 @@ outline: deep
 
 # api
 
-- **Type:** `boolean | number | object`
-- **Default:** `false`
-- **CLI:** `--api`, `--api.port`, `--api.host`, `--api.strictPort`
+- **类型:** `boolean | number | object`
+- **默认值:** `false`
+- **命令行终端:** `--api`, `--api.port`, `--api.host`, `--api.strictPort`
 
 Listen to port and serve API for [the UI](/guide/ui) or [browser server](/guide/browser/). When set to `true`, the default port is `51204`.
 
 ## api.allowWrite <Version>4.1.0</Version> {#api-allowwrite}
 
-- **Type:** `boolean`
-- **Default:** `true` if not exposed to the network, `false` otherwise
+- **类型:** `boolean`
+- **默认值:** `true` if not exposed to the network, `false` otherwise
 
 Vitest server can save test files or snapshot files via the API. This allows anyone who can connect to the API the ability to run any arbitrary code on your machine.
 
@@ -28,7 +28,7 @@ If the host is set to anything other than `localhost` or `127.0.0.1`, Vitest wil
 
 ## api.allowExec <Version>4.1.0</Version> {#api-allowexec}
 
-- **Type:** `boolean`
-- **Default:** `true` if not exposed to the network, `false` otherwise
+- **类型:** `boolean`
+- **默认值:** `true` if not exposed to the network, `false` otherwise
 
 Allows running any test file via the API. See the security advice in [`api.allowWrite`](#api-allowwrite).

config/attachmentsdir.md

@@ -5,7 +5,7 @@ outline: deep
 
 # attachmentsDir
 
-- **Type:** `string`
-- **Default:** `'.vitest-attachments'`
+- **类型:** `string`
+- **默认值:** `'.vitest-attachments'`
 
 Directory path for storing attachments created by [`context.annotate`](/guide/test-context#annotate) relative to the project root.

config/bail.md

@@ -5,8 +5,8 @@ outline: deep
 
 # bail
 
-- **Type:** `number`
-- **Default:** `0`
+- **类型:** `number`
+- **默认值:** `0`
 - **CLI**: `--bail=<value>`
 
 Stop test execution when given number of tests have failed.

config/benchmark.md

@@ -1,5 +1,5 @@
 ---
-title: benchmark | Config
+title: benchmark | 配置
 outline: deep
 ---
 

config/browser/api.md

@@ -7,24 +7,24 @@ outline: deep
 
 # browser.api
 
-- **Type:** `number | object`
-- **Default:** `63315`
-- **CLI:** `--browser.api=63315`, `--browser.api.port=1234, --browser.api.host=example.com`
+- **类型:** `number | object`
+- **默认值:** `63315`
+- **命令行终端:** `--browser.api=63315`, `--browser.api.port=1234, --browser.api.host=example.com`
 
 Configure options for Vite server that serves code in the browser. Does not affect [`test.api`](/config/api) option. By default, Vitest assigns port `63315` to avoid conflicts with the development server, allowing you to run both in parallel.
 
 ## api.allowWrite <Version>4.1.0</Version> {#api-allowwrite}
 
-- **Type:** `boolean`
-- **Default:** `true` if not exposed to the network, `false` otherwise
+- **类型:** `boolean`
+- **默认值:** `true` if not exposed to the network, `false` otherwise
 
 Vitest saves [annotation attachments](/guide/test-annotations), [artifacts](/api/advanced/artifacts) and [snapshots](/guide/snapshot) by receiving a WebSocket connection from the browser. This allows anyone who can connect to the API write any arbitary code on your machine within the root of your project (configured by [`fs.allow`](https://vite.dev/config/server-options#server-fs-allow)).
 
 If browser server is not exposed to the internet (the host is `localhost`), this should not be a problem, so the default value in that case is `true`. If you override the host, Vitest will set `allowWrite` to `false` by default to prevent potentially harmful writes.
 
 ## api.allowExec <Version>4.1.0</Version> {#api-allowexec}
 
-- **Type:** `boolean`
-- **Default:** `true` if not exposed to the network, `false` otherwise
+- **类型:** `boolean`
+- **默认值:** `true` if not exposed to the network, `false` otherwise
 
 Allows running any test file via the UI. This only applies to the interactive elements (and the server code behind them) in the [UI](/guide/ui) that can run the code. If UI is disabled, this has no effect. See [`api.allowExec`](/config/api#api-allowexec) for more information.

config/browser/commands.md

@@ -5,7 +5,7 @@ outline: deep
 
 # browser.commands
 
-- **Type:** `Record<string, BrowserCommand>`
-- **Default:** `{ readFile, writeFile, ... }`
+- **类型:** `Record<string, BrowserCommand>`
+- **默认值:** `{ readFile, writeFile, ... }`
 
 Custom [commands](/api/browser/commands) that can be imported during browser tests from `vitest/browser`.

config/browser/connecttimeout.md

@@ -5,8 +5,8 @@ outline: deep
 
 # browser.connectTimeout
 
-- **Type:** `number`
-- **Default:** `60_000`
+- **类型:** `number`
+- **默认值:** `60_000`
 
 The timeout in milliseconds. If connection to the browser takes longer, the test suite will fail.
 

config/browser/detailspanelposition.md

@@ -7,9 +7,9 @@ outline: deep
 
 # browser.detailsPanelPosition
 
-- **Type:** `'right' | 'bottom'`
-- **Default:** `'right'`
-- **CLI:** `--browser.detailsPanelPosition=bottom`, `--browser.detailsPanelPosition=right`
+- **类型:** `'right' | 'bottom'`
+- **默认值:** `'right'`
+- **命令行终端:** `--browser.detailsPanelPosition=bottom`, `--browser.detailsPanelPosition=right`
 
 Controls the default position of the details panel in the Vitest UI when running browser tests.
 

config/browser/enabled.md

@@ -4,9 +4,9 @@ title: browser.enabled | Config
 
 # browser.enabled
 
-- **Type:** `boolean`
-- **Default:** `false`
-- **CLI:** `--browser`, `--browser.enabled=false`
+- **类型:** `boolean`
+- **默认值:** `false`
+- **命令行终端:** `--browser`, `--browser.enabled=false`
 
 Enabling this flag makes Vitest run all tests in a [browser](/guide/browser/) by default. If you are configuring other browser options via the CLI, you can use `--browser.enabled` alongside them instead of `--browser`:
 

config/browser/expect.md

@@ -5,7 +5,7 @@ outline: deep
 
 # browser.expect
 
-- **Type:** `ExpectOptions`
+- **类型:** `ExpectOptions`
 
 ## browser.expect.toMatchScreenshot
 
@@ -48,7 +48,7 @@ available: `resolveScreenshotPath` and `resolveDiffPath`.
 
 ## browser.expect.toMatchScreenshot.resolveScreenshotPath
 
-- **Type:** `(data: PathResolveData) => string`
+- **类型:** `(data: PathResolveData) => string`
 - **Default output:** `` `${root}/${testFileDirectory}/${screenshotDirectory}/${testFileName}/${arg}-${browserName}-${platform}${ext}` ``
 
 A function to customize where reference screenshots are stored. The function
@@ -127,7 +127,7 @@ resolveScreenshotPath: ({ arg, browserName, ext, root, testFileName }) =>
 
 ## browser.expect.toMatchScreenshot.resolveDiffPath
 
-- **Type:** `(data: PathResolveData) => string`
+- **类型:** `(data: PathResolveData) => string`
 - **Default output:** `` `${root}/${attachmentsDir}/${testFileDirectory}/${testFileName}/${arg}-${browserName}-${platform}${ext}` ``
 
 A function to customize where diff images are stored when screenshot comparisons
@@ -143,7 +143,7 @@ resolveDiffPath: ({ arg, attachmentsDir, browserName, ext, root, testFileName })
 
 ## browser.expect.toMatchScreenshot.comparators
 
-- **Type:** `Record<string, Comparator>`
+- **类型:** `Record<string, Comparator>`
 
 Register custom screenshot comparison algorithms, like [SSIM](https://en.wikipedia.org/wiki/Structural_similarity_index_measure) or other perceptual similarity metrics.
 

config/browser/headless.md

@@ -5,8 +5,8 @@ outline: deep
 
 # browser.headless
 
-- **Type:** `boolean`
-- **Default:** `process.env.CI`
-- **CLI:** `--browser.headless`, `--browser.headless=false`
+- **类型:** `boolean`
+- **默认值:** `process.env.CI`
+- **命令行终端:** `--browser.headless`, `--browser.headless=false`
 
 Run the browser in a `headless` mode. If you are running Vitest in CI, it will be enabled by default.

config/browser/instances.md

@@ -5,8 +5,8 @@ outline: deep
 
 # browser.instances
 
-- **Type:** `BrowserConfig`
-- **Default:** `[]`
+- **类型:** `BrowserConfig`
+- **默认值:** `[]`
 
 Defines multiple browser setups. Every config has to have at least a `browser` field.
 

config/browser/isolate.md

@@ -5,9 +5,9 @@ outline: deep
 
 # browser.isolate <Deprecated />
 
-- **Type:** `boolean`
-- **Default:** the same as [`--isolate`](/config/isolate)
-- **CLI:** `--browser.isolate`, `--browser.isolate=false`
+- **类型:** `boolean`
+- **默认值:** the same as [`--isolate`](/config/isolate)
+- **命令行终端:** `--browser.isolate`, `--browser.isolate=false`
 
 Run every test in a separate iframe.
 

config/browser/orchestratorscripts.md

@@ -5,8 +5,8 @@ outline: deep
 
 # browser.orchestratorScripts
 
-- **Type:** `BrowserScript[]`
-- **Default:** `[]`
+- **类型:** `BrowserScript[]`
+- **默认值:** `[]`
 
 Custom scripts that should be injected into the orchestrator HTML before test iframes are initiated. This HTML document only sets up iframes and doesn't actually import your code.
 

config/browser/playwright.md

@@ -160,8 +160,8 @@ await userEvent.click(page.getByRole('button'), {
 
 ## `persistentContext` <Version>4.1.0</Version> {#persistentcontext}
 
-- **Type:** `boolean | string`
-- **Default:** `false`
+- **类型:** `boolean | string`
+- **默认值:** `false`
 
 When enabled, Vitest uses Playwright's [persistent context](https://playwright.dev/docs/api/class-browsertype#browser-type-launch-persistent-context) instead of a regular browser context. This allows browser state (cookies, localStorage, DevTools settings, etc.) to persist between test runs.
 

config/browser/provider.md

@@ -5,7 +5,7 @@ outline: deep
 
 # browser.provider {#browser-provider}
 
-- **Type:** `BrowserProviderOption`
+- **类型:** `BrowserProviderOption`
 
 The return value of the provider factory. You can import the factory from `@vitest/browser-<provider-name>` or make your own provider:
 

config/browser/screenshotfailures.md

@@ -5,7 +5,7 @@ outline: deep
 
 # browser.screenshotFailures
 
-- **Type:** `boolean`
-- **Default:** `!browser.ui`
+- **类型:** `boolean`
+- **默认值:** `!browser.ui`
 
 Should Vitest take screenshots if the test fails.

config/browser/testerhtmlpath.md

@@ -5,6 +5,6 @@ outline: deep
 
 # browser.testerHtmlPath
 
-- **Type:** `string`
+- **类型:** `string`
 
 A path to the HTML entry point. Can be relative to the root of the project. This file will be processed with [`transformIndexHtml`](https://vite.dev/guide/api-plugin#transformindexhtml) hook.

config/browser/trace.md

@@ -5,9 +5,9 @@ outline: deep
 
 # browser.trace
 
-- **Type:** `'on' | 'off' | 'on-first-retry' | 'on-all-retries' | 'retain-on-failure' | object`
-- **CLI:** `--browser.trace=on`, `--browser.trace=retain-on-failure`
-- **Default:** `'off'`
+- **类型:** `'on' | 'off' | 'on-first-retry' | 'on-all-retries' | 'retain-on-failure' | object`
+- **命令行终端:** `--browser.trace=on`, `--browser.trace=retain-on-failure`
+- **默认值:** `'off'`
 
 Capture a trace of your browser test runs. You can preview traces with [Playwright Trace Viewer](https://trace.playwright.dev/).
 

config/browser/trackunhandlederrors.md

@@ -5,8 +5,8 @@ outline: deep
 
 # browser.trackUnhandledErrors
 
-- **Type:** `boolean`
-- **Default:** `true`
+- **类型:** `boolean`
+- **默认值:** `true`
 
 Enables tracking uncaught errors and exceptions so they can be reported by Vitest.
 

config/browser/ui.md

@@ -5,8 +5,8 @@ outline: deep
 
 # browser.ui
 
-- **Type:** `boolean`
-- **Default:** `!isCI`
-- **CLI:** `--browser.ui=false`
+- **类型:** `boolean`
+- **默认值:** `!isCI`
+- **命令行终端:** `--browser.ui=false`
 
 Should Vitest UI be injected into the page. By default, injects UI iframe during development.

config/chaiconfig.md

@@ -5,29 +5,29 @@ outline: deep
 
 # chaiConfig
 
-- **Type:** `{ includeStack?, showDiff?, truncateThreshold? }`
-- **Default:** `{ includeStack: false, showDiff: true, truncateThreshold: 40 }`
+- **类型:** `{ includeStack?, showDiff?, truncateThreshold? }`
+- **默认值:** `{ includeStack: false, showDiff: true, truncateThreshold: 40 }`
 
 Equivalent to [Chai config](https://github.com/chaijs/chai/blob/4.x.x/lib/chai/config.js).
 
 ## chaiConfig.includeStack
 
-- **Type:** `boolean`
-- **Default:** `false`
+- **类型:** `boolean`
+- **默认值:** `false`
 
 Influences whether stack trace is included in Assertion error message. Default of false suppresses stack trace in the error message.
 
 ## chaiConfig.showDiff
 
-- **Type:** `boolean`
-- **Default:** `true`
+- **类型:** `boolean`
+- **默认值:** `true`
 
 Influences whether or not the `showDiff` flag should be included in the thrown AssertionErrors. `false` will always be `false`; `true` will be true when the assertion has requested a diff to be shown.
 
 ## chaiConfig.truncateThreshold
 
-- **Type:** `number`
-- **Default:** `40`
+- **类型:** `number`
+- **默认值:** `40`
 
 Sets length threshold for actual and expected values in assertion errors. If this threshold is exceeded, for example for large data structures, the value is replaced with something like `[ Array(3) ]` or `{ Object (prop1, prop2) }`. Set it to `0` if you want to disable truncating altogether.
 

config/clearmocks.md

@@ -5,8 +5,8 @@ outline: deep
 
 # clearMocks
 
-- **Type:** `boolean`
-- **Default:** `false`
+- **类型:** `boolean`
+- **默认值:** `false`
 
 Should Vitest automatically call [`vi.clearAllMocks()`](/api/vi#vi-clearallmocks) before each test.