From 8b84e1f056e7aaf1e5394f007cbc849e9b3f9f30 Mon Sep 17 00:00:00 2001 From: Localhousee Date: Mon, 17 Oct 2022 05:28:56 +0700 Subject: [PATCH] docs: `resolve.alias` link from docs (#2160) --- docs/guide/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/index.md b/docs/guide/index.md index 218c569412ba..ca074fc5a0f4 100644 --- a/docs/guide/index.md +++ b/docs/guide/index.md @@ -35,7 +35,7 @@ Vitest requires Vite >=v2.7.10 and Node >=v14 ## Configuring Vitest -One of the main advantages of Vitest is its unified configuration with Vite. If present, `vitest` will read your root `vite.config.ts` to match with the plugins and setup as your Vite app. For example, your Vite [resolve.alias](https://vitejs.dev/config/#resolve-alias) and [plugins](https://vitejs.dev/guide/using-plugins.html) configuration will work out-of-the-box. If you want a different configuration during testing, you can: +One of the main advantages of Vitest is its unified configuration with Vite. If present, `vitest` will read your root `vite.config.ts` to match with the plugins and setup as your Vite app. For example, your Vite [resolve.alias](https://vitejs.dev/config/shared-options.html#resolve-alias) and [plugins](https://vitejs.dev/guide/using-plugins.html) configuration will work out-of-the-box. If you want a different configuration during testing, you can: - Create `vitest.config.ts`, which will have the higher priority - Pass `--config` option to CLI, e.g. `vitest --config ./path/to/vitest.config.ts`