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
Different jest.jestCommandLine settings for run vs debug #1081
Comments
In debug, vscode uses its own configuration in the |
Feature request
I'm using
fnm
on Linux to select my node version, and I've managed to setjest.jestCommandLine
insettings.json
to use the correct Node version according to the.nvmrc
in my project:This works fine for running tests normally (in the Jest 'Testing' activity), and from using 'Run test'.
However, when I use the 'Debug test' shortcut, e.g. to debug a specific test, it uses
jest.jestCommandLine
in a weird way; it prepends the full path of my system default Node binary (which is not the binary used for my project; that's an older Node version), so I get something like this:This of course gives me a
Cannot find module
error, sincefnm
isn't something Node can run.In this case, it'd be useful if we could use a different
jest.jestCommandLine
value for run and debug, since the value is used differently in each context.The relevant line seems to be:
vscode-jest/src/JestExt/core.ts
Line 636 in 10414ab
Workaround
For now, I'll just use
fnm default x
to set the Node version globally.The text was updated successfully, but these errors were encountered: