Replies: 2 comments
-
Unfortunately, I do not have an environment like this to test in and there isn't enough information to troubleshoot with what's provided. However; I suspect it has to do with #1068 |
Beta Was this translation helpful? Give feedback.
-
This is indeed related to #1068 The workaround is to launch a new powershell console, like so: #1120 seems to fix it, but has not been approved. |
Beta Was this translation helpful? Give feedback.
-
Operating system and version: Windows Server 2019 Std
nvm debug output:
Details
Windows PowerShell Windows Version: 10.0 (Build 17763)
Windows Developer Mode: UNKNOWN (user cannot read registry)
NVM4W Version: 1.1.12
NVM4W Path: C:\ProgramData\nvm\nvm.exe
NVM4W Settings: C:\ProgramData\nvm\settings.txt
NVM_HOME: C:\ProgramData\nvm
NVM_SYMLINK: C:\Program Files\nodejs
Node Installations: C:\ProgramData\nvm
Total Node.js Versions: 1
Active Node.js Version: v20.11.1
No problems detected.
Find help at https://github.com/coreybutler/nvm-windows/wiki/Common-Issues
nvm ls output:
Details
How did you install nvm?
using nvm-windows (nvm-setup.exe) version 1.1.12
What steps did you perform?
Double click installed from nvm-setp.exe, then npm install latest
What is working?
Installed and configured nvm and can use locally from server using powershell and cmd
What is not working?
nvm commands to work from azure devops pipeline or PSSession remote but it doesn't respond for ever
Azure DevOps Version and Agent used:
Azure DevOps Server 2019.1.1
Agent version used: 2.200.0
NVM version: 1.1.12
Everything works with:
Azure DevOps Server 2019.1.1
Agent version used: 2.200.0
NVM version: 1.1.11
Beta Was this translation helpful? Give feedback.
All reactions