vscode-jest: env: node: No such file or directory

If you have installed node using nvm, it won’t be in the place this extension expects it to be (/usr/bin/env).

Workaround

You can make sure it is in the relative path by launching vscode in the root directory of your project:

cd ~/my-project
code .

If this is happening to you on a Mac, with iTerm and Zsh. I had to set the Explorer Kind (terminal application to use) in VSCode to external

Also, make sure this is not overridden at the Workspace level settings.

The plugin was just updated to 2.2.0 and the issue seems to have been resolved! Thanks ❤️

I’m using VSCode with WSL and also struggled this issue.

If there is anyone like me, here is the solution:

1. Put ~/.vscode-server/server-env-setup or ~/.vscode-server/server-env-setup in your WSL. see: https://code.visualstudio.com/docs/remote/wsl#_advanced-environment-setup-script

2. Write below in theserver-env-setup file:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm

these lines are copied from my ~/.bashrc.

1. Restart WSL session in VSCode

FWIW, for nvm users

this workaround https://github.com/jest-community/vscode-jest/issues/105#issuecomment-469971991 (quoted below) works well, provided that you don’t have any kind of lazy loading mechanism in place for nvm.

👉 lazy loading nvm is not recommended by its authors (see this 2016 comment https://github.com/nvm-sh/nvm/issues/730#issuecomment-226949107)

Lazy loading examples

Via zsh-nvm

This might be the case if you’ve installed nvm via the zsh-nvm plugin and then, for perf. reasons decided to opt in for lazy loading (exporting the NVM_LAZY_LOAD environment variable). For more info, see : https://github.com/lukechilds/zsh-nvm#lazy-loading

Example of a manual setup

# Add every binary that requires nvm, npm or node to run to an array of node globals
NODE_GLOBALS=(`find ~/.nvm/versions/node -maxdepth 3 -type l -wholename '*/bin/*' | xargs -n1 basename | sort | uniq`)
NODE_GLOBALS+=("node")
NODE_GLOBALS+=("nvm")

# Lazy-loading nvm + npm on node globals call
load_nvm () {
  export NVM_DIR=~/.nvm
  [ -s "$(brew --prefix nvm)/nvm.sh" ] && . "$(brew --prefix nvm)/nvm.sh"
}

# Making node global trigger the lazy loading
for cmd in "${NODE_GLOBALS[@]}"; do
  eval "${cmd}(){ unset -f ${NODE_GLOBALS}; load_nvm; ${cmd} \$@ }"
done

src: https://gist.github.com/fl0w/07ce79bd44788f647deab307c94d6922

Workaround https://github.com/jest-community/vscode-jest/issues/105#issuecomment-469971991

If you have installed node using nvm, it won’t be in the place this extension expects it to be (/usr/bin/env).

Workaround

You can make sure it is in the relative path by launching vscode in the root directory of your project:

cd ~/my-project
code .

@kevin-lindsay-1 this might be the reason why, regarding your setup, you didn’t manage to find a working solution.

placing these nvm in profile/zshrc solves it for me…

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm

Same issue, this should be reopened

I am commenting here because I just got this error and this page was the first one to pop up on my search.

I use nvm on macOS and sometimes got this error, what did worked for me was to change the node version via nvm. Just change it to some other version and then change it back to the version you wanted.

do it using vscode terminal

nvm use [version other than your current one]
nvm use [your version here]

close vscode (really close it, not reload or click on the X, quit it complete) and open it gain.

No sure the reason, but I guess should be related about things already said: lazy loading, OS update that erase some settings or shell did not load node in time.

Fixed this issue by set the vscode config: Terminal>Integrated: Inherit Env. to true.

I’m getting the same error, strangely this extension has been working perfectly for the last months. I recently added a create-react-app app inside my project, with its own package.json file and everything. Whenever I open VSCode from there code /react-app/. Jest suddenly stops working.

I installed node with Homebrew:

$ which node
/usr/local/bin/node

But this doesn’t seem to be an issue when opening VSCode from the “parent” folder…

Oh, very cool, I bet this is because CRA-TS would have different defaults than CRA wrt the Jest testRegex - once this is using Jest version 20, it should work with the newest release I think