From cec9d7103ac34bc32fcb692d83c9cb4b9a35d987 Mon Sep 17 00:00:00 2001 From: Emmanuel Ferdman Date: Sun, 5 May 2024 16:30:40 +0300 Subject: [PATCH] docs: Fix `wxt-vitest-plugin` reference (#650) Signed-off-by: Emmanuel Ferdman --- docs/guide/testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/testing.md b/docs/guide/testing.md index 535d3bfb..2494b3bc 100644 --- a/docs/guide/testing.md +++ b/docs/guide/testing.md @@ -22,4 +22,4 @@ If you want to try to use a different framework for unit tests, you will need to - **Global Variables**: If you consume them, manually define globals provided by WXT (like `import.meta.env.BROWSER`) by adding them to the global scope before accessing them (`import.meta.env.BROWSER = "chrome"`) - **Import paths**: If you use the `@/` or `~/` path aliases, add them to your test environment -[Here's how Vitest is configured](https://github.com/wxt-dev/wxt/blob/main/src/testing/wxt-vitest-plugin.ts) for reference. +[Here's how Vitest is configured](https://github.com/wxt-dev/wxt/blob/main/packages/wxt/src/testing/wxt-vitest-plugin.ts) for reference.