docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 66a9b6b6

.vitepress/components.d.ts

@@ -8,7 +8,9 @@ export {}
 /* prettier-ignore */
 declare module 'vue' {
   export interface GlobalComponents {
+    ArrowDown: typeof import('./components/ArrowDown.vue')['default']
     BlogIndex: typeof import('./components/BlogIndex.vue')['default']
+    Box: typeof import('./components/Box.vue')['default']
     Contributors: typeof import('./components/Contributors.vue')['default']
     CourseLink: typeof import('./components/CourseLink.vue')['default']
     FeaturesList: typeof import('./components/FeaturesList.vue')['default']

.vitepress/components/ArrowDown.vue

@@ -0,0 +1,27 @@
+<template>
+  <span class="arrow-down">
+    <span class="arrow-line" />
+    <span class="arrow-head" />
+  </span>
+</template>
+
+<style scoped>
+.arrow-down {
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+}
+
+.arrow-line {
+  height: 1rem;
+  width: 0.2rem;
+  background-color: var(--vp-c-brand-1);
+}
+
+.arrow-head {
+  height: 1rem;
+  width: 1rem;
+  background-color: var(--vp-c-brand-1);
+  clip-path: polygon(100% 0, 0 0, 50% 100%);
+}
+</style>

.vitepress/components/Box.vue

@@ -0,0 +1,18 @@
+<template>
+  <span class="box">
+    <slot />
+  </span>
+</template>
+
+<style scoped>
+.box {
+  display: flex;
+  width: 100%;
+  align-items: center;
+  justify-content: center;
+  text-align: center;
+  border: 0.1rem solid var(--vp-c-brand-1);
+  border-radius: 15px;
+  padding: 1rem 2rem;
+}
+</style>

.vitepress/components/FeaturesList.vue

@@ -1,87 +1,28 @@
 <template>
-  <ul class="features-list" dir="auto" flex="~ col gap2 md:gap-3">
-    <ListItem>
-      与
-      <a target="_blank" href="https://vitejs.dev" rel="noopener noreferrer">Vite</a>
-      通用的配置、转换器、解析器和插件。
-    </ListItem>
-    <ListItem>使用与你的应用相同的设置来运行测试！</ListItem>
-    <ListItem>智能文件监听模式，就像是测试的 HMR！</ListItem>
-    <ListItem>支持对 Vue、React、Svelte、Lit等框架进行组件测试。</ListItem>
+  <ul
+    class="features-list"
+    dir="auto"
+    flex="~ col gap2 md:gap-3"
+  >
+    <ListItem>使用 <a target="_blank" href="https://vitejs.dev" rel="noopener noreferrer">Vite</a> 的配置、转换器、解析器和插件</ListItem>
+    <ListItem>使用与应用程序相同的设置来运行测试！</ListItem>
+    <ListItem>智能即时监听模式，如同测试的热模块替换！</ListItem>
+    <ListItem>支持 Vue、React、Svelte、Lit、Marko 等组件测试</ListItem>
     <ListItem>开箱即用的 TypeScript / JSX 支持</ListItem>
-    <ListItem>ESM 优先，支持模块顶级 await</ListItem>
-    <ListItem>
-      通过
-      <a
-        target="_blank"
-        href="https://github.com/tinylibs/tinypool"
-        rel="noopener noreferrer"
-      >Tinypool</a>
-      使用 Worker 线程尽可能多地并发运行
-    </ListItem>
-    <ListItem>
-      使用
-      <a
-        target="_blank"
-        href="https://github.com/tinylibs/tinybench"
-        rel="noopener noreferrer"
-      >Tinybench</a>
-      来支持基准测试
-    </ListItem>
-    <ListItem>套件和测试的过滤、超时、并发配置</ListItem>
-    <ListItem>支持 <a href="/guide/workspace">Workspace</a></ListItem>
-    <ListItem>
-      <a href="/guide/snapshot"> Jest 的快照功能 </a>
-    </ListItem>
-    <ListItem>
-      内置
-      <a target="_blank" href="https://www.chaijs.com/" rel="nofollow">Chai</a>
-      进行断言 + 与
-      <a href="https://jestjs.io/zh-Hans/docs/expect" rel="nofollow">Jest expect 语法</a>兼容的 API
-    </ListItem>
-    <ListItem>
-      内置用于对象模拟(Mock)的
-      <a
-        target="_blank"
-        href="https://github.com/Aslemammad/tinyspy"
-        rel="nofollow"
-      >Tinyspy</a>
-    </ListItem>
-    <ListItem>
-      使用
-      <a target="_blank" href="https://github.com/jsdom/jsdom">jsdom</a> 或
-      <a target="_blank" href="https://github.com/capricorn86/happy-dom">happy-dom</a>
-      用于 DOM 模拟
-    </ListItem>
-    <ListItem><a href="https://vitest.dev/guide/browser/" rel="noopener noreferrer">浏览器模式</a> 用于在浏览器中运行组件测试</ListItem>
-    <ListItem>
-      通过
-      <a
-        target="_blank"
-        href="https://v8.dev/blog/javascript-code-coverage"
-        rel="noopener noreferrer"
-      >v8</a>
-      or
-      <a
-        target="_blank"
-        href="https://istanbul.js.org/"
-        rel="noopener noreferrer"
-      >istanbul</a>来输出代码测试覆盖率
-    </ListItem>
-    <ListItem>
-      类似于 Rust 语言的
-      <a target="_blank" href="https://cn.vitest.dev/guide/in-source.html">源码内联测试</a>
-    </ListItem>
-    <ListItem>
-      通过
-      <a
-        target="_blank"
-        href="https://github.com/mmkal/expect-type"
-        rel="noopener noreferrer"
-      >expect-type</a>
-      进行类型测试
-    </ListItem>
-    <ListItem>支持分片</ListItem>
+    <ListItem>ESM 优先，支持顶级 await</ListItem>
+    <ListItem>通过 <a target="_blank" href="https://github.com/tinylibs/tinypool" rel="noopener noreferrer">Tinypool</a> 实现 Worker 多线程</ListItem>
+    <ListItem>使用 <a target="_blank" href="https://github.com/tinylibs/tinybench" rel="noopener noreferrer">Tinybench</a> 进行基准测试</ListItem>
+    <ListItem>支持测试套件和测试的过滤、超时、并发</ListItem>
+    <ListItem>支持<a href="/guide/projects">多项目</a></ListItem>
+    <ListItem>内置 <a target="_blank" href="https://www.chaijs.com/" rel="noopener noreferrer">Chai</a> 断言库 + 兼容 <a target="_blank" href="https://jestjs.io/docs/expect" rel="noopener noreferrer">Jest expect</a> API</ListItem>
+    <ListItem>内置 <a target="_blank" href="https://github.com/tinylibs/tinyspy" rel="noopener noreferrer">Tinyspy</a> 用于模拟</ListItem>
+    <ListItem>使用 <a target="_blank" href="https://github.com/capricorn86/happy-dom" rel="noopener noreferrer">happy-dom</a> 或 <a target="_blank" href="https://github.com/jsdom/jsdom" rel="noopener noreferrer">jsdom</a> 进行 DOM 模拟</ListItem>
+    <ListItem><a href="https://vitest.dev/guide/browser/" rel="noopener noreferrer">浏览器模式</a>用于在浏览器中运行组件测试</ListItem>
+    <ListItem>通过 <a target="_blank" href="https://v8.dev/blog/javascript-code-coverage" rel="noopener noreferrer">v8</a> 或 <a target="_blank" href="https://istanbul.js.org/" rel="noopener noreferrer">istanbul</a> 进行代码覆盖率检测</ListItem>
+    <ListItem>类似 Rust 的<a href="/guide/in-source">源码内测试</a></ListItem>
+    <ListItem>通过 <a target="_blank" href="https://github.com/mmkal/expect-type" rel="noopener noreferrer">expect-type</a> 进行类型测试</ListItem>
+    <ListItem>分片支持</ListItem>
+    <ListItem>未捕获错误报告</ListItem>
   </ul>
 </template>
 

.vitepress/config.ts

@@ -469,8 +469,8 @@ function guide(): DefaultTheme.SidebarItem[] {
       link: '/guide/filtering',
     },
     {
-      text: '工作空间',
-      link: '/guide/workspace',
+      text: '测试项目',
+      link: '/guide/projects',
     },
     {
       text: '报告器「Reporters」',
@@ -488,6 +488,10 @@ function guide(): DefaultTheme.SidebarItem[] {
       text: '模拟对象',
       link: '/guide/mocking',
     },
+    {
+      text: 'Parallelism',
+      link: '/guide/parallelism',
+    },
     {
       text: '类型测试',
       link: '/guide/testing-types',
@@ -504,6 +508,10 @@ function guide(): DefaultTheme.SidebarItem[] {
       text: '测试上下文',
       link: '/guide/test-context',
     },
+    {
+      text: '测试注释',
+      link: '/guide/test-annotations',
+    },
     {
       text: '测试环境',
       link: '/guide/environment',

.vitepress/sponsors.ts

@@ -17,9 +17,9 @@ const vitestSponsors = {
       img: '/nuxtlabs.svg',
     },
     {
-      name: 'Stackblitz',
-      url: 'https://stackblitz.com',
-      img: '/stackblitz.svg',
+      name: 'Bolt',
+      url: 'https://bolt.new',
+      img: '/bolt.svg',
     },
     {
       name: 'Zammad',

advanced/api/index.md

@@ -119,7 +119,7 @@ const { vitestConfig, viteConfig } = await resolveConfig({
 :::
 
 ::: warning
-`resolveConfig` 不会解析 `workspace`。要解析工作区配置，Vitest 需要一个已建立的 Vite 服务器。
+`resolveConfig` 不能解析 `projects` 。为了解决项目配置， Vitest 需要一个已建立的 Vite 服务器。
 
 另外请注意，`viteConfig.test` 不会被完全解析。如果你需要 Vitest 配置，请使用 `vitestConfig` 代替。
 :::

advanced/api/plugin.md

@@ -53,7 +53,7 @@ Vitest 通过  `Vite` namespace 重新导出所有仅 Vite 类型的导入，我
 ```
 :::
 
-与 [`reporter.onInit`](/advanced/api/reporters#oninit) 不同，此 hooks 在 Vitest 生命周期的早期运行，允许我们更改 `coverage` 和 `reporters` 等配置。更值得注意的变化是，如果我们的插件是在项目中定义而不是在全局配置中定义的，我们可以从 [工作区项目](/guide/workspace) 操作全局配置。
+与 [`reporter.onInit`](/advanced/api/ reporter#oninit) 不同，这个 hook 在 Vitest 生命周期的早期运行，允许我们对`coverage`和`reporters`等配置进行更改。一个更值得注意的变化是，如果我们的插件是在项目中定义的而不是在全局配置中，我们可以从 [test project](/guide/projects) 中操作全局配置。
 
 ## Context
 
@@ -93,10 +93,10 @@ function injectTestProjects(
 ```ts
 // inject a single project with a custom alias
 const newProjects = await injectTestProjects({
-  // you can inherit the current project config by referencing `configFile`
+  // you can inherit the current project config by referencing `extends`
   // note that you cannot have a project with the name that already exists,
   // so it's a good practice to define a custom name
-  configFile: project.vite.config.configFile,
+  extends: project.vite.config.configFile,
   test: {
     name: 'my-custom-alias',
     alias: {
@@ -107,7 +107,11 @@ const newProjects = await injectTestProjects({
 ```
 
 ::: warning Projects are Filtered
+<<<<<<< HEAD
 Vitest 在配置解析期间过滤项目，因此如果用户定义了过滤器，则注入的项目可能无法解析，除非它 [与 filter 匹配](./vitest#matchesprojectfilter)。我们可以通过 `vitest.config.project` 选项更新过滤器，以始终包含我们的工作区项目：
+=======
+Vitest filters projects during the config resolution, so if the user defined a filter, injected project might not be resolved unless it [matches the filter](./vitest#matchesprojectfilter). You can update the filter via the `vitest.config.project` option to always include your test project:
+>>>>>>> 66a9b6b6b1842fb5487d24c3e913f0ebfd55103b
 
 ```ts
 vitest.config.project.push('my-project-name')
@@ -117,7 +121,11 @@ vitest.config.project.push('my-project-name')
 :::
 
 ::: tip Referencing the Current Config
+<<<<<<< HEAD
 如果我们想保留用户配置，可以指定 `configFile` 属性。所有其他属性都将与用户定义的配置合并。
+=======
+If you want to keep the user configuration, you can specify the `extends` property. All other properties will be merged with the user defined config.
+>>>>>>> 66a9b6b6b1842fb5487d24c3e913f0ebfd55103b
 
 项目的 `configFile` 可以在 Vite 的配置中访问：`project.vite.config.configFile`。
 

advanced/api/reporters.md

@@ -15,6 +15,7 @@ Vitest 拥有自己的测试运行生命周期。这些生命周期通过报告
       - [`onHookStart(beforeAll)`](#onhookstart)
       - [`onHookEnd(beforeAll)`](#onhookend)
         - [`onTestCaseReady`](#ontestcaseready)
+          - [`onTestAnnotate`](#ontestannotate) <Version>3.2.0</Version>
           - [`onHookStart(beforeEach)`](#onhookstart)
           - [`onHookEnd(beforeEach)`](#onhookend)
           - [`onHookStart(afterEach)`](#onhookstart)
@@ -316,4 +317,21 @@ function onTestCaseResult(testCase: TestCase): Awaitable<void>
 
 当测试完成运行或刚刚被跳过时调用此方法。请注意，如果有 `afterEach` 钩子，这将在 `afterEach` 钩子完成后调用。
 
+<<<<<<< HEAD
 此时，[`testCase.result()`](/advanced/api/test-case#result) 将具有非挂起状态。
+=======
+At this point, [`testCase.result()`](/advanced/api/test-case#result) will have non-pending state.
+
+## onTestAnnotate <Version>3.2.0</Version> {#ontestannotate}
+
+```ts
+function onTestAnnotate(
+  testCase: TestCase,
+  annotation: TestAnnotation,
+): Awaitable<void>
+```
+
+The `onTestAnnotate` hook is associated with the [`context.annotate`](/guide/test-context#annotate) method. When `annotate` is invoked, Vitest serialises it and sends the same attachment to the main thread where reporter can interact with it.
+
+If the path is specified, Vitest stores it in a separate directory (configured by [`attachmentsDir`](/config/#attachmentsdir)) and modifies the `path` property to reference it.
+>>>>>>> 66a9b6b6b1842fb5487d24c3e913f0ebfd55103b

advanced/api/test-module.md

@@ -95,5 +95,18 @@ interface ModuleDiagnostic {
    * This value is only available if the test was executed with `logHeapUsage` flag.
    */
   readonly heap: number | undefined
+  /**
+   * The time spent importing every non-externalized dependency that Vitest has processed.
+   */
+  readonly importDurations: Record<string, ImportDuration>
+}
+
+/** The time spent importing & executing a non-externalized file. */
+interface ImportDuration {
+  /** The time spent importing & executing the file itself, not counting all non-externalized imports that the file does. */
+  selfTime: number
+
+  /** The time spent importing & executing the file and all its imports. */
+  totalTime: number
 }
 ```