Jest process "watch-tests" ended unexpectedly: npm not found

[Morriz]

Environment

1. vscode-jest version: v4.4.0
2. node -v: v16.14.2
3. npm -v or yarn --version: 8.5.0
4. npm ls jest or npm ls react-scripts (if you haven’t ejected): react-scripts@5.0.1
5. your vscode-jest settings if customized:
   • jest.jestCommandLine? [fill]
   • jest.autoRun? [fill]
   • anything else that you think might be relevant? [fill]
6. Operating system: OSX 12.3.1

Prerequisite

• are you able to run jest test from the command line? yes
• how do you run your tests from the command line? npm test which runs react-scripts test

Steps to Reproduce

Open a react-scripts project that has the extension installed. Only upon startup is an error shown, and the waiting script re-runs successfully after touching any file. Race condition?

Also, setting a custom command is giving the same errors.

The jest config:

module.exports = {
  preset: 'ts-jest',
  testEnvironment: 'node',
  modulePathIgnorePatterns: ['.history'],
  transform: {
    '^.+\\.test.(ts|tsx)?$': 'ts-jest',
  },
  moduleFileExtensions: ['ts', 'tsx', 'js', 'jsx', 'json', 'node'],
}

Relevant Debug Info

Without configuring anything (out of the box) I see this error:

not-test onProcessExit: process exit with code=127, signal=undefined
 see troubleshooting: https://github.com/jest-community/vscode-jest/blob/master/README.md#troubleshooting
/bin/sh: npm: command not found
Jest process "watch-tests" ended unexpectedly
 see troubleshooting: https://github.com/jest-community/vscode-jest/blob/master/README.md#troubleshooting

Expected Behavior

No error messages

Actual Behavior

Error messages

---

The fastest (and the most fun) way to resolve the issue is to submit a pull-request yourself. If you are interested, feel free to check out the contribution guide, we look forward to seeing your PR...

[Morriz]

I tried uninstalling, cleaning prefs, reinstalling, but no dice.

[Morriz]

We use the same config in another repo where these errors don't appear. I am trying to find out what is diff

[connectdotz]

/bin/sh: npm: command not found

this usually indicates a shell env issue. Try to start vscode from a terminal (instead of UI).

more detailed info here

[Morriz]

I always start it from shell, and all my windows work fine. If the app can't find npm in PATH then I presume PATH must be different suddenly. Hmmm

[connectdotz]

you can verify the path via the developer console:

See additional logging from the developer console (via Help > Toggle Developer Tools menu), look for the spawn log, expand the "options" object, then "env", the "PATH" (inherited from vscode process) should be there:

[Morriz]

ok, got vscode updates and the issue is gone...may have been some local state that got corrupt. Tnx for your time