Skip to content
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

Unable to start extension #392

Closed
4 tasks done
joyceli214 opened this issue May 22, 2024 · 3 comments · Fixed by #411
Closed
4 tasks done

Unable to start extension #392

joyceli214 opened this issue May 22, 2024 · 3 comments · Fixed by #411
Labels
documentation Improvements or additions to documentation

Comments

@joyceli214
Copy link

Describe the bug

Hi all, I am new to vite and just trying to get my tests running. However, when I tried to start the extension, it always resulted in the same error below

I am using below versions
vscode 1.89.0
vscode extension 0.10.7

I have tried

  • uninstall and re-install extension
  • kill and reopen vscode
  • restart computer
    but none of them works

Reproduction

https://github.com/vitest-dev/vitest/tree/main/examples/basic
I have tried with the example code from vitest and also could not start the extension (running npm test can run tests tho

Output

[INFO 11:16:07 AM] [v0.10.7] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 11:16:10 AM] [API] Running Vitest: v1.6.0 (vite.config.ts)
[INFO 11:16:10 AM] [API] Starting Vitest process with Node.js: C:\Program Files (x86)\nodejs\node.EXE
[Error 11:16:18 AM] [Error Error] Vitest failed to start: 

r
Error: Vitest failed to start: 

r
    at ChildProcess.f (c:\Users\[my username]\.vscode\extensions\vitest.explorer-0.10.7\dist\extension.js:19:333)
    at ChildProcess.emit (node:events:517:28)
    at emit (node:internal/child_process:944:14)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

Version

0.10.7

Validations

@nadihsu
Copy link

nadihsu commented May 22, 2024

I encountered the same problem in vitest@0.10.7

@joyceli214
Copy link
Author

I seemed to have gotten the extension running after upgrading node version from 16.15.1 to 20.13.1. Maybe could consider adding compatible node versions to the docs?

@sheremet-va
Copy link
Member

sheremet-va commented May 22, 2024

Vitest requires Node 18+ which is mentioned in its documentation.

I guess we can check the version in the extension before spawning Vitest

@sheremet-va sheremet-va added documentation Improvements or additions to documentation and removed pending triage labels Jun 5, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jun 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
3 participants