-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always getting Error: spawn ENOTDIR
when opening a workspace that has Vitest
#383
Comments
I get this too. But only sporadically. When I then run a particular test again, it sometimes passes, but not always. My tests use |
I don't use |
Alright, so unrelated to dotenv. No idea why it is happening then. The weird part is even that if I run all my tests, sometimes it'll happen only for a subset of the tests. So hard to repro though 😄 |
Do you have Node available globally? What shell do you use by default? What does |
When I run I am running inside a DevContainer. The image is based on the |
Yes I have Node available globally. |
This comment put me on the right path. If I open a I normally open VSC workspace files through the Finder, so I'd appreciate if that's fixed, thanks! |
I am not using workspaces at all. But for me it also only happens sporadically. When it happens, I just have to retry running the test a couple of more times, and it'll work again. |
Is reported output the full output? I don't understand why it doesn't report the current |
Added more logs in 0.10.6 |
Posted new logs here,
|
Describe the bug
I open a workspace in VSC that has Vitest. I get the error as seen below.
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.Otherwise, the extension still seems to work fine.
This issue seems different from #381 since I don't use NVM.
Reproduction
Output
The text was updated successfully, but these errors were encountered: