Currently it's not possible to use the vitest VS Code extension in the repo since Vitest v1.4.0 or newer is required.
As of this posting we're using Vitest v1.3.1 in some parts of the repo, and v0.34 in others.
~Vitest v1 doesn't support changing directories in worker threads, so we'll need to find a workaround or rewrite tests in the repo that use APIs like process.chdir() (see https://github.com/vitest-dev/vitest/issues/1436)~
Edit: It looks like the CLI options changed (--no-threads isn't available anymore), so now you can use --pool forks as a workaround
Currently it's not possible to use the vitest VS Code extension in the repo since Vitest v1.4.0 or newer is required.
As of this posting we're using Vitest v1.3.1 in some parts of the repo, and v0.34 in others.
~Vitest v1 doesn't support changing directories in worker threads, so we'll need to find a workaround or rewrite tests in the repo that use APIs like
process.chdir()
(see https://github.com/vitest-dev/vitest/issues/1436)~Edit: It looks like the CLI options changed (
--no-threads
isn't available anymore), so now you can use--pool forks
as a workaround