Asking for nvm to be installed, when it is already

[DOHere]

macOS Big Sur 11.5.2
VSCode 1.60.1

.vscode/launch.json:

{    "configurations": [
    {
        "runtimeVersion": "10.16.3",
        "type": "node",
        "request": "launch",
        "name": "Launch Program",
        "skipFiles": [
            "<node_internals>/**"
        ],
        "program": "${workspaceFolder}/engineRun.js",
        "args": ["3000"],
        "console": "integratedTerminal"
    }
]}

This used to run before. And note that terminal run: "node engineRun.js 3000" works.
But when I run VSCode's "Launch program", with the launch file above, I get:

Attribute 'runtimeVersion' requires Node.js version manager 'nvs' or 'nvm' to be installed.

I do have nvm installed + that node version

[Jkovarik]

Confirming I'm also having this issue after updating to 1.60.1.

[connor4312]

What's the value of the NVM_HOME environment variable, and does it exist?

[DOHere]

What's the value of the NVM_HOME environment variable, and does it exist?

Hi! There's no NVM_HOME, but there is an NVM_DIR (I run that at the end here):

my.acc~/Desktop/myRepo$ echo $NVM_HOME

my.acc~/Desktop/myRepo$ nvm --version
0.34.0

my.acc~/Desktop/myRepo$ nvm -v

Node Version Manager

Note: refers to any version-like string nvm understands. This includes:

• full or partial version numbers, starting with an optional "v" (0.10, v0.1.2, v1)
• default (built-in) aliases: node, stable, unstable, iojs, system
• custom aliases you define with nvm alias foo

Any options that produce colorized output should respect the --no-colors option.

Usage:
nvm --help Show this message
nvm --version Print out the installed version of nvm
nvm install [-s] Download and install a , [-s] from source. Uses .nvmrc if available
--reinstall-packages-from= When installing, reinstall packages installed in <node|iojs|node version number>
--lts When installing, only select from LTS (long-term support) versions
--lts= When installing, only select from versions for a specific LTS line
--skip-default-packages When installing, skip the default-packages file if it exists
--latest-npm After installing, attempt to upgrade to the latest working npm on the given node version
--no-progress Disable the progress bar on any downloads
nvm uninstall Uninstall a version
nvm uninstall --lts Uninstall using automatic LTS (long-term support) alias lts/*, if available.
nvm uninstall --lts= Uninstall using automatic alias for provided LTS line, if available.
nvm use [--silent] Modify PATH to use . Uses .nvmrc if available
--lts Uses automatic LTS (long-term support) alias lts/*, if available.
--lts= Uses automatic alias for provided LTS line, if available.
nvm exec [--silent] [] Run on . Uses .nvmrc if available
--lts Uses automatic LTS (long-term support) alias lts/*, if available.
--lts= Uses automatic alias for provided LTS line, if available.
nvm run [--silent] [] Run node on with as arguments. Uses .nvmrc if available
--lts Uses automatic LTS (long-term support) alias lts/*, if available.
--lts= Uses automatic alias for provided LTS line, if available.
nvm current Display currently activated version of Node
nvm ls List installed versions
nvm ls List versions matching a given
nvm ls-remote List remote versions available for install
--lts When listing, only show LTS (long-term support) versions
nvm ls-remote List remote versions available for install, matching a given
--lts When listing, only show LTS (long-term support) versions
--lts= When listing, only show versions for a specific LTS line
nvm version Resolve the given description to a single local version
nvm version-remote Resolve the given description to a single remote version
--lts When listing, only select from LTS (long-term support) versions
--lts= When listing, only select from versions for a specific LTS line
nvm deactivate Undo effects of nvm on current shell
nvm alias [] Show all aliases beginning with
nvm alias Set an alias named pointing to
nvm unalias Deletes the alias named
nvm install-latest-npm Attempt to upgrade to the latest working npm on the current node version
nvm reinstall-packages Reinstall global npm packages contained in to current version
nvm unload Unload nvm from shell
nvm which [current | ] Display path to installed node version. Uses .nvmrc if available
nvm cache dir Display path to the cache directory for nvm
nvm cache clear Empty cache directory for nvm

Example:
nvm install 8.0.0 Install a specific version number
nvm use 8.0 Use the latest available 8.0.x release
nvm run 6.10.3 app.js Run app.js using node 6.10.3
nvm exec 4.8.3 node app.js Run node app.js with the PATH pointing to node 4.8.3
nvm alias default 8.1.0 Set default node version on a shell
nvm alias default node Always default to the latest available node version on a shell

Note:
to remove, delete, or uninstall nvm - just remove the $NVM_DIR folder (usually ~/.nvm)

my.acc~/Desktop/myRepo$ echo $NVM_DIR
/Users/my.acc/.nvm

[connor4312]

Hm, ok. If you remove the runtimeVersion and console so that the node script is run as a subprocess of the extension host, is NVM_DIR set there? I'm wondering if the environment variable isn't getting applied to VS Code.

If that isn't set, where do you have nvm configured? (Which .rc file?)

[DOHere]

Hm, ok. If you remove the runtimeVersion and console so that the node script is run as a subprocess of the extension host, is NVM_DIR set there? I'm wondering if the environment variable isn't getting applied to VS Code.

If that isn't set, where do you have nvm configured? (Which .rc file?)

If I remove runtime version and console from the launch file again, it still won't run (with the same error).

my.acc~/Desktop/myRepo$ nvm which
No .nvmrc file found

Node Version Manager

Note: refers to any version-like string nvm understands. This includes:

• full or partial version numbers, starting with an optional "v" (0.10, v0.1.2, v1)
• default (built-in) aliases: node, stable, unstable, iojs, system
• custom aliases you define with nvm alias foo

Any options that produce colorized output should respect the --no-colors option.

Usage:
nvm --help Show this message
nvm --version Print out the installed version of nvm
nvm install [-s] Download and install a , [-s] from source. Uses .nvmrc if available
--reinstall-packages-from= When installing, reinstall packages installed in <node|iojs|node version number>
--lts When installing, only select from LTS (long-term support) versions
--lts= When installing, only select from versions for a specific LTS line
--skip-default-packages When installing, skip the default-packages file if it exists
--latest-npm After installing, attempt to upgrade to the latest working npm on the given node version
--no-progress Disable the progress bar on any downloads
nvm uninstall Uninstall a version
nvm uninstall --lts Uninstall using automatic LTS (long-term support) alias lts/*, if available.
nvm uninstall --lts= Uninstall using automatic alias for provided LTS line, if available.
nvm use [--silent] Modify PATH to use . Uses .nvmrc if available
--lts Uses automatic LTS (long-term support) alias lts/*, if available.
--lts= Uses automatic alias for provided LTS line, if available.
nvm exec [--silent] [] Run on . Uses .nvmrc if available
--lts Uses automatic LTS (long-term support) alias lts/*, if available.
--lts= Uses automatic alias for provided LTS line, if available.
nvm run [--silent] [] Run node on with as arguments. Uses .nvmrc if available
--lts Uses automatic LTS (long-term support) alias lts/*, if available.
--lts= Uses automatic alias for provided LTS line, if available.
nvm current Display currently activated version of Node
nvm ls List installed versions
nvm ls List versions matching a given
nvm ls-remote List remote versions available for install
--lts When listing, only show LTS (long-term support) versions
nvm ls-remote List remote versions available for install, matching a given
--lts When listing, only show LTS (long-term support) versions
--lts= When listing, only show versions for a specific LTS line
nvm version Resolve the given description to a single local version
nvm version-remote Resolve the given description to a single remote version
--lts When listing, only select from LTS (long-term support) versions
--lts= When listing, only select from versions for a specific LTS line
nvm deactivate Undo effects of nvm on current shell
nvm alias [] Show all aliases beginning with
nvm alias Set an alias named pointing to
nvm unalias Deletes the alias named
nvm install-latest-npm Attempt to upgrade to the latest working npm on the current node version
nvm reinstall-packages Reinstall global npm packages contained in to current version
nvm unload Unload nvm from shell
nvm which [current | ] Display path to installed node version. Uses .nvmrc if available
nvm cache dir Display path to the cache directory for nvm
nvm cache clear Empty cache directory for nvm

Example:
nvm install 8.0.0 Install a specific version number
nvm use 8.0 Use the latest available 8.0.x release
nvm run 6.10.3 app.js Run app.js using node 6.10.3
nvm exec 4.8.3 node app.js Run node app.js with the PATH pointing to node 4.8.3
nvm alias default 8.1.0 Set default node version on a shell
nvm alias default node Always default to the latest available node version on a shell

Note:
to remove, delete, or uninstall nvm - just remove the $NVM_DIR folder (usually ~/.nvm)

So I added a .nvmrc file to my repo:

my.acc~/Desktop/myRepo$ node -v > .nvmrc

my.acc~/Desktop/myRepo$ cat .nvmrc
v10.15.0

Still the same error when I run VsCode debugging tho:(. Btw, this is my .bashrc config:

my.acc~/Desktop/myRepo$ cat $HOME/.bashrc
npm set prefix ~/.npm
PATH="$HOME/.npm/bin:$PATH"
PATH="./node_modules/.bin:$PATH"

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

[connor4312]

@bpasero how does environment variable resolution for the extension host work now? Could the NVM_DIR in their bashrc not be picked up for some reason or another?

[bpasero]

@connor4312 via this service call:

vscode/src/vs/workbench/services/extensions/electron-browser/localProcessExtensionHost.ts

Line 209 in a0a448f

this._shellEnvironmentService.getShellEnv(),

[Anshorei]

Encountered this problem as well. It was introduced in v1.60.0, and I have found no solution other than to downgrade to v1.59.1

[connor4312]

Do you happen to have nvs also installed?

I'm not able to reproduce this on my machine, and the code js-debug uses is almost identical to the old debugger. It would be super helpful if someone could step through the code here to see what's happening on their machine and why it's not being detected: https://github.com/microsoft/vscode-js-debug/blob/db286867c4d6b797304a5a0ef05cce01c3c35b08/src/targets/node/nvmResolver.ts#L51. Contributing guide here for setup info.

[dcastellanos-r7]

I have the same issue and nvs is not installed on my system.
$NVM_DIR is set to /Users/my_user/.nvm

[DOHere]

Do you happen to have nvs also installed?

I'm not able to reproduce this on my machine, and the code js-debug uses is almost identical to the old debugger. It would be super helpful if someone could step through the code here to see what's happening on their machine and why it's not being detected: https://github.com/microsoft/vscode-js-debug/blob/db286867c4d6b797304a5a0ef05cce01c3c35b08/src/targets/node/nvmResolver.ts#L51. Contributing guide here for setup info.

I also don't have nvs installed. And I'm not using Windows(as that code mentions), but a MacOS.