···2525})
2626```
27272828+The `<reference types="vitest" />` will stop working in Vitest 3, but you can start migrating to `vitest/config` in Vitest 2.1:
2929+3030+```ts
3131+/// <reference types="vitest/config" />
3232+import { defineConfig } from 'vite'
3333+3434+export default defineConfig({
3535+ test: {
3636+ // ... Specify options here.
3737+ },
3838+})
3939+```
4040+2841Using `defineConfig` from `vitest/config` you should follow this:
29423043```ts
+4-6
docs/guide/in-source.md
···3434Update the `includeSource` config for Vitest to grab the files under `src/`:
35353636```ts
3737-// vite.config.ts
3838-/// <reference types="vitest" />
3939-import { defineConfig } from 'vite'
3737+// vitest.config.ts
3838+import { defineConfig } from 'vitest/config'
40394140export default defineConfig({
4241 test: {
···5655For the production build, you will need to set the `define` options in your config file, letting the bundler do the dead code elimination. For example, in Vite
57565857```ts
5959-// vite.config.ts
6060-/// <reference types="vitest" />
6161-import { defineConfig } from 'vite'
5858+// vitest.config.ts
5959+import { defineConfig } from 'vitest/config'
62606361export default defineConfig({
6462 test: {
+13
docs/guide/index.md
···133133})
134134```
135135136136+The `<reference types="vitest" />` will stop working in Vitest 3, but you can start migrating to `vitest/config` in Vitest 2.1:
137137+138138+```ts
139139+/// <reference types="vitest/config" />
140140+import { defineConfig } from 'vite'
141141+142142+export default defineConfig({
143143+ test: {
144144+ // ... Specify options here.
145145+ },
146146+})
147147+```
148148+136149See the list of config options in the [Config Reference](../config/)
137150138151::: warning
+1-2
docs/guide/reporters.md
···1616Using reporters via [`vitest.config.ts`](/config/):
17171818```ts
1919-/// <reference types="vitest" />
2020-import { defineConfig } from 'vite'
1919+import { defineConfig } from 'vitest/config'
21202221export default defineConfig({
2322 test: {