Merge branch 'vitest-dev:main' into main

Author: jgillick

.gitattributes

@@ -1,3 +1,3 @@
 * text=auto eol=lf
 
-test/reporters/fixtures/indicator-position.test.js eol=crlf
+test/cli/fixtures/reporters/indicator-position.test.js eol=crlf

.github/workflows/ci.yml

@@ -223,7 +223,7 @@ jobs:
 
       - name: Install
         run: |
-          yq -i '.overrides.vite = "npm:rolldown-vite"' pnpm-workspace.yaml
+          yq -i '.overrides.vite = "npm:vite@beta"' pnpm-workspace.yaml
           git add . && git commit -m "ci" && pnpm i --prefer-offline --no-frozen-lockfile
 
       - uses: ./.github/actions/setup-playwright

README.md

@@ -78,6 +78,12 @@ $ npx vitest
 
 ## Sponsors
 
+<p align="center">
+  <a href="https://cdn.jsdelivr.net/gh/sheremet-va/static/vitest/sponsors.svg">
+    <img src='https://cdn.jsdelivr.net/gh/sheremet-va/static/vitest/sponsors.svg'/>
+  </a>
+</p>
+
 ### Vladimir Sponsors
 
 <p align="center">

docs/.vitepress/config.ts

@@ -730,6 +730,10 @@ export default ({ mode }: { mode: string }) => {
                 text: 'Test Environment',
                 link: '/guide/environment',
               },
+              {
+                text: 'Test Run Lifecycle',
+                link: '/guide/lifecycle',
+              },
               {
                 text: 'Snapshot',
                 link: '/guide/snapshot',
@@ -858,7 +862,7 @@ export default ({ mode }: { mode: string }) => {
           },
           {
             text: 'Advanced',
-            collapsed: true,
+            collapsed: false,
             items: [
               {
                 text: 'Getting Started',
@@ -947,7 +951,7 @@ export default ({ mode }: { mode: string }) => {
           },
           {
             text: 'Advanced',
-            collapsed: true,
+            collapsed: false,
             items: [
               {
                 text: 'Vitest',

docs/.vitepress/sponsors.ts

@@ -29,7 +29,13 @@ const vitestSponsors = {
       img: '/zammad.svg',
     },
   ],
-  // platinum: [],
+  platinum: [
+    {
+      name: 'Chromatic',
+      url: 'https://www.chromatic.com/?utm_source=vitest&utm_medium=sponsorship&utm_campaign=vitestSponsorship',
+      img: '/logo-chromatic.svg',
+    },
+  ],
   gold: [
     {
       name: 'vital',
@@ -51,11 +57,6 @@ const vitestSponsors = {
       url: 'https://www.liminity.se/',
       img: '/liminity.svg',
     },
-    {
-      name: 'Bytebase',
-      url: 'https://www.bytebase.com/',
-      img: '/bytebase.svg',
-    },
   ],
 } satisfies Record<string, Sponsor[]>
 
@@ -70,11 +71,11 @@ export const sponsors = [
     size: 'big',
     items: vitestSponsors.special,
   },
-  // {
-  //   tier: 'Platinum Sponsors',
-  //   size: 'big',
-  //   items: vitestSponsors.platinum,
-  // },
+  {
+    tier: 'Platinum Sponsors',
+    size: 'big',
+    items: vitestSponsors.platinum,
+  },
   {
     tier: 'Gold Sponsors',
     size: 'medium',

docs/api/advanced/reporters.md

@@ -36,7 +36,7 @@ Note that since test modules can run in parallel, Vitest will report them in par
 This guide lists all supported reporter methods. However, don't forget that instead of creating your own reporter, you can [extend existing one](/guide/advanced/reporters) instead:
 
 ```ts [custom-reporter.js]
-import { BaseReporter } from 'vitest/reporters'
+import { BaseReporter } from 'vitest/node'
 
 export default class CustomReporter extends BaseReporter {
   onTestRunEnd(testModules, errors) {

docs/api/advanced/runner.md

@@ -106,14 +106,12 @@ export interface VitestRunner {
 When initiating this class, Vitest passes down Vitest config, - you should expose it as a `config` property:
 
 ```ts [runner.ts]
-import type { RunnerTestFile } from 'vitest'
-import type { VitestRunner, VitestRunnerConfig } from 'vitest/suite'
-import { VitestTestRunner } from 'vitest/runners'
+import type { RunnerTestFile, SerializedConfig, TestRunner, VitestTestRunner } from 'vitest'
 
-class CustomRunner extends VitestTestRunner implements VitestRunner {
-  public config: VitestRunnerConfig
+class CustomRunner extends TestRunner implements VitestTestRunner {
+  public config: SerializedConfig
 
-  constructor(config: VitestRunnerConfig) {
+  constructor(config: SerializedConfig) {
     this.config = config
   }
 
@@ -281,17 +279,15 @@ Vitest exposes `createTaskCollector` utility to create your own `test` method. I
 A task is an object that is part of a suite. It is automatically added to the current suite with a `suite.task` method:
 
 ```js [custom.js]
-import { createTaskCollector, getCurrentSuite } from 'vitest/suite'
-
-export { afterAll, beforeAll, describe } from 'vitest'
+export { afterAll, beforeAll, describe, TestRunner } from 'vitest'
 
 // this function will be called during collection phase:
 // don't call function handler here, add it to suite tasks
 // with "getCurrentSuite().task()" method
 // note: createTaskCollector provides support for "todo"/"each"/...
-export const myCustomTask = createTaskCollector(
+export const myCustomTask = TestRunner.createTaskCollector(
   function (name, fn, timeout) {
-    getCurrentSuite().task(name, {
+    TestRunner.getCurrentSuite().task(name, {
       ...this, // so "todo"/"skip"/... is tracked correctly
       meta: {
         customPropertyToDifferentiateTask: true

docs/api/advanced/test-suite.md

@@ -200,12 +200,11 @@ function meta(): TaskMeta
 Custom [metadata](/api/advanced/metadata) that was attached to the suite during its execution or collection. The meta can be attached by assigning a property to the `suite.meta` object during a test run:
 
 ```ts {7,12}
-import { test } from 'vitest'
-import { getCurrentSuite } from 'vitest/suite'
+import { describe, test, TestRunner } from 'vitest'
 
 describe('the validation works correctly', () => {
   // assign "decorated" during collection
-  const { suite } = getCurrentSuite()
+  const { suite } = TestRunner.getCurrentSuite()
   suite!.meta.decorated = true
 
   test('some test', ({ task }) => {

docs/api/expect.md

@@ -1758,7 +1758,7 @@ You can use `expect.not` with this matcher to negate the expected value.
 
 This method adds custom serializers that are called when creating a snapshot. This is an advanced feature - if you want to know more, please read a [guide on custom serializers](/guide/snapshot#custom-serializer).
 
-If you are adding custom serializers, you should call this method inside [`setupFiles`](/config/#setupfiles). This will affect every snapshot.
+If you are adding custom serializers, you should call this method inside [`setupFiles`](/config/setupfiles). This will affect every snapshot.
 
 :::tip
 If you previously used Vue CLI with Jest, you might want to install [jest-serializer-vue](https://www.npmjs.com/package/jest-serializer-vue). Otherwise, your snapshots will be wrapped in a string, which cases `"` to be escaped.
@@ -1793,7 +1793,7 @@ test('custom matchers', () => {
 ```
 
 ::: tip
-If you want your matchers to appear in every test, you should call this method inside [`setupFiles`](/config/#setupfiles).
+If you want your matchers to appear in every test, you should call this method inside [`setupFiles`](/config/setupfiles).
 :::
 
 This function is compatible with Jest's `expect.extend`, so any library that uses it to create custom matchers will work with Vitest.

docs/api/vi.md

@@ -42,7 +42,7 @@ Substitutes all imported modules from provided `path` with another module. You c
 
 In order to hoist `vi.mock`, Vitest statically analyzes your files. It indicates that `vi` that was not directly imported from the `vitest` package (for example, from some utility file) cannot be used. Use `vi.mock` with `vi` imported from `vitest`, or enable [`globals`](/config/#globals) config option.
 
-Vitest will not mock modules that were imported inside a [setup file](/config/#setupfiles) because they are cached by the time a test file is running. You can call [`vi.resetModules()`](#vi-resetmodules) inside [`vi.hoisted`](#vi-hoisted) to clear all module caches before running a test file.
+Vitest will not mock modules that were imported inside a [setup file](/config/setupfiles) because they are cached by the time a test file is running. You can call [`vi.resetModules()`](#vi-resetmodules) inside [`vi.hoisted`](#vi-hoisted) to clear all module caches before running a test file.
 :::
 
 If the `factory` function is defined, all imports will return its result. Vitest calls factory only once and caches results for all subsequent imports until [`vi.unmock`](#vi-unmock) or [`vi.doUnmock`](#vi-dounmock) is called.
@@ -168,7 +168,7 @@ axios.get(`/apples/${increment(1)}`)
 ```
 
 ::: warning
-Beware that if you don't call `vi.mock`, modules **are not** mocked automatically. To replicate Jest's automocking behaviour, you can call `vi.mock` for each required module inside [`setupFiles`](/config/#setupfiles).
+Beware that if you don't call `vi.mock`, modules **are not** mocked automatically. To replicate Jest's automocking behaviour, you can call `vi.mock` for each required module inside [`setupFiles`](/config/setupfiles).
 :::
 
 If there is no `__mocks__` folder or a factory provided, Vitest will import the original module and auto-mock all its exports. For the rules applied, see [algorithm](/guide/mocking/modules#automocking-algorithm).