-
|
Hello! I am having some trouble running the extension. VS Code version: 1.92.1 I seem to have the requirements needed, but as soon as I open my repo, I get an error message telling me something went wrong. When I click to see the error, I get a bunch of failures in the Has anyone seen this before? Can you recommend how to fix this? I have tried updating Vitest, but the same thing occurs and 1.4.0 is the minimum at which this should work, I believe. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
I'm getting the exact same error. Baffled as to how to fix it. Any help? |
Beta Was this translation helpful? Give feedback.
-
|
I finally figured out why this was happening. I had recently renamed my all-lowercase project directory to use camel-case instead (for example, "myproject" became "myProject"). VSCode still had the path as "myproject" so the code in the vitest extension that's designed to detect and avoid recursion when scanning for test files was unable to tell the difference and kept recursing down until it got to the root of my HD. Removing the project from VSCode and creating a new project by selecting the renamed directory fixed the problem. |
Beta Was this translation helpful? Give feedback.
-
|
This worked for me too! Thank you for coming back and sharing! |
Beta Was this translation helpful? Give feedback.
I finally figured out why this was happening.
I had recently renamed my all-lowercase project directory to use camel-case instead (for example, "myproject" became "myProject").
VSCode still had the path as "myproject" so the code in the vitest extension that's designed to detect and avoid recursion when scanning for test files was unable to tell the difference and kept recursing down until it got to the root of my HD.
Removing the project from VSCode and creating a new project by selecting the renamed directory fixed the problem.