Closed MangelMaxime closed 2 months ago
The extension expects either the config or a script
in package.json
that starts with vitest
. Starting Vitest for any project seems excessive. What if you have vitest installed globally?
What if you have vitest installed globally?
I would say this is a bad practice 😝
More seriously, I understand the reason behind the decision you are describing. Perhaps the log can be changed to explain the situation / requirements or make these requirements documented somewhere?
If they are sorry I was not able to find it.
Describe the bug
Vitest VSCode fails to start without a Vitest config file.
I am pretty sure in the past it was able to start without a config file. Also I found https://github.com/vitest-dev/vscode/issues/348 mentioning the same issue and having a fix provided for it. So perhaps this is a regression.
Reproduction
Open a repository without a Vitest config file.
Output
Version
v0.10.2
Validations