search

firsttris / vscode-jest-runner

Simple way to run or debug one or more tests from context menu, codelens or command plalette
https://marketplace.visualstudio.com/items?itemName=firsttris.vscode-jest-runner
MIT License
265 stars 124 forks source link

When debugging, Can't find Can't find Node.js binary "node": path does not exist... #175

Closed jjm340 closed 3 years ago

jjm340 commented 3 years ago

With the latest version of VSCode, I just started receiving the error message: Can't find Node.js binary "node": path does not exist. Make sure Node.js is installed and in your PATH, or set the "runtimeExecutable" in your launch.json.

This worked fine up until the last update of VSCode it seems.

firsttris commented 3 years ago

hey @jjm340 thx for reporting.

how can i reproduce your issue?

i simply have node installed nothing configured in launch.json

maybe re-check if your issue still persists in version 0.4.35

firsttris commented 3 years ago

re-open if issue still persists with version 0.4.38

jjm340 commented 3 years ago

Problem went away on it's own!

iamogbz commented 3 years ago

For anyone else having this issue this was how I fixed it in my use-case. Add to your user/workspace settings:

    "jestrunner.debugOptions": {
      "runtimeExecutable": "/absolute/path/to/node"
    }

This was on extension v0.4.44, with node available in my terminal and the vscode-jest-runner run command working but the debug command failing with the above error message, and vscode running the workspace from a remote ssh env

jjm340 commented 3 years ago

Is this option documented? If not, might be nice to have it there.

floroz commented 3 years ago

For anyone else having this issue this was how I fixed it in my use-case. Add to your user/workspace settings:

    "jestrunner.debugOptions": {
      "runtimeExecutable": "/absolute/path/to/node"
    }

This was on extension v0.4.44, with node available in my terminal and the vscode-jest-runner run command working but the debug command failing with the above error message, and vscode running the workspace from a remote ssh env

Thank you, had the same issue and this solved it for me!