monorepo shouldn't require a root installation of vitest

[samuelstroschein]

Problem

It's unclear which vitest version is used for packages.

• The VSCode extension forces the installation of votes at the root of the repo, even if a workspace is defined.

• This can lead to vitest versions running out of sync. A test run with the vitest CLI in a package uses the vitest version defined in the package-a/package.json while the VSCode extension uses the vitest version at the root of the monorepo.

• We have been battling flaky tests for months in https://github.com/opral/monorepo. I don't know if the vitest vscode extension and out of sync versions are to blame or something else.

Expected behavior

The VSCode extension picks up the vitest version from the projects and does not require a vitest installation at the root of the repo.

[sheremet-va]

You have a vitest workspace file in the root of your monorepo. What vitest should be used to process it? The file can only be imported by the vitest process itself.

If you don't use it, don't have the file.

[samuelstroschein]

Should work but the next bug popped up. One project failing leads the entire Vitest VSCode extension to crash.

• parrot-figma crashes vitest extension "command not found"
• vscode extension completely shuts off

Expected behavior

If one project fails to load, other projects should still process/proceed.

---

This is prob exactly why the workspaces are useful. In the workspace, we ignore parrot-figma. We don't have the possibility to ignore parrot figma without the workspace, and without the workspace the vscode extension is yielding flaky runs that differ from the CLI

[samuelstroschein]

The real solution seems to be:

1. define a workspace
2. the vscode extension resolves vite and vitest from the package, not from a global install

[sheremet-va]

If one project fails to load, other projects should still process/proceed.

Sure, we can do that, feel free to open an issue.

the vscode extension resolves vite and vitest from the package, not from a global install

Vitest needs to read the workspace file, it's not the extension that reads it. To do that, it needs to be installed.

[sheremet-va]

You can also exclude certain configs with vitest.configSearchPatternExclude option, by the way

[samuelstroschein]

Not pressing atm, providing the video as "this is how the bugs looks like" but can't reproduce it so far outside of our repo

EDIT: restarting vscode makes the vscode extension mark the test as passing. Maybe a caching issue?

CleanShot.2025-05-06.at.23.13.43.mp4