Closed fehmer closed 2 months ago
Is this a new issue? I just installed the Vitest extension a few days ago, and I get this error every time I open a workspace in VSC. Is there a previous version of this extension I can roll back to for now, that doesn't have this issue?
Edit: Okay, I can see that the issue starts with v0.8.0 of this extension. So I'm using 0.6.3 for now. Presumably caused by this change.
Is there something I can change to fix this on my end? I've got Node installed globally on my Mac, v20.11.0, at /usr/local/bin/node
. I don't use nvm.
The funny thing is the extension still seems to work fine.
I also use nvm
and it's working fine. The reproduction is not enough. What does which node
return when you run it in a terminal? What OS are you using?
Thanks for the reply. The issue was how I openened vscode. Opening it from a commandline works.
Thanks for the reply. The issue was how I openened vscode. Opening it from a commandline works.
This put me on the right path... I've posted my issue in #383.
Describe the bug
i'm using ubuntu linux and don't have a nodejs version installed globally but use
nvm
.On opening vscode there is a popup
There was an error during Vitest startup.
and the output is this:Best solution would be to use the default node version from nvm. If this is not possible improve the error message like
Cannot find node executable, set vitest.nodeExecutable configuration in your workspace or make sure node is installed at <expected-path>
Reproduction
Output
Version
0.10.2
Validations