You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ nvm list
v8.17.0
v10.22.0
-> v12.22.1
v14.17.0
v16.3.0
…
launch.json:
{// Use IntelliSense to learn about possible attributes.// Hover to view descriptions of existing attributes.// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387"version": "0.2.0","configurations": [{"type": "node","request": "launch","name": "Jest","program": "${workspaceRoot}/node_modules/.bin/jest","args": ["--color"],"outputCapture": "std","runtimeVersion": "16"}]}
Running this debug task fails with "Node.js version '16' cannot be found for 'nvm'":
However, if the value of runtimeVersion to a specific version I have installed ("runtimeVersion": "16.3.0" in this case), the debug task runs as expected.
If you omit the minor and patch version and have, for example, "runtimeVersion": "14", then the most recent 14.x.y version installed on your system will be used.
So my understanding here is that 16.3.0 should be used in this setup and should not error.
VS Code version: Code 1.58.0 (2d23c42, 2021-07-08T06:54:55.083Z)
OS version: Windows_NT x64 10.0.19041
Restricted Mode: No
Remote OS version: Linux x64 5.4.72-microsoft-standard-WSL2
Remote OS version: Linux x64 5.4.72-microsoft-standard-WSL2
System Info
Item
Value
CPUs
Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz (4 x 3292)
You'll need to set your launch type to pwa-node for this to work. The old node type is redirected through the previous debugger, but only after it tries (and failed) to resolve that version number. This'll no longer be necessary when the old debugger (eventually) goes away entirely.
Issue Type: Bug
launch.json:
Running this debug task fails with "Node.js version '16' cannot be found for 'nvm'":
However, if the value of
runtimeVersion
to a specific version I have installed ("runtimeVersion": "16.3.0"
in this case), the debug task runs as expected.I believe this is a bug since the Multi version support section of Node.js debugging documentation states that:
So my understanding here is that
16.3.0
should be used in this setup and should not error.VS Code version: Code 1.58.0 (2d23c42, 2021-07-08T06:54:55.083Z)
OS version: Windows_NT x64 10.0.19041
Restricted Mode: No
Remote OS version: Linux x64 5.4.72-microsoft-standard-WSL2
Remote OS version: Linux x64 5.4.72-microsoft-standard-WSL2
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: