From b75f91d26529d7c6a09bd1d9149e8672c5de978e Mon Sep 17 00:00:00 2001 From: Vladimir Sheremet Date: Wed, 13 Sep 2023 10:14:43 +0200 Subject: [PATCH] docs: remove outdated statement --- docs/api/vi.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/api/vi.md b/docs/api/vi.md index 5aa3eb5263ef..86afb2681313 100644 --- a/docs/api/vi.md +++ b/docs/api/vi.md @@ -433,12 +433,6 @@ import.meta.env.MODE = 'test' ``` ::: -:::warning -Vitest transforms all `import.meta.env` calls into `process.env`, so they can be easily changed at runtime. Node.js only supports string values as env parameters, while Vite supports several built-in envs as boolean (namely, `SSR`, `DEV`, `PROD`). To mimic Vite, set "truthy" values as env: `''` instead of `false`, and `'1'` instead of `true`. - -But beware that you cannot rely on `import.meta.env.DEV === false` in this case. Use `!import.meta.env.DEV`. This also affects simple assigning, not just `vi.stubEnv` method. -::: - ## vi.unstubAllEnvs - **Type:** `() => Vitest`