[Issue]: spaces in the installation path of nvm lead to errors using it
PurpleMagick opened this issue · 4 comments
What happened?
Attempting to change the node versions with nvm use there is an error because of the space in the installation directory.
Note that nvm install does work without producing errors. Only nvm use shows an issue.
What did you expect to happen?
Switching the used version of Node should work even if there are spaces in the path. I found issue #41 which is closed (and issue #168 which is a duplicate of it) which claims this was addressed. Te common issues page says spaces in path names should work as of 1.1.8
Version
1.1.11 or newer (Default)
Which version of Windows?
Windows 10 (Default)
Which locale?
English (Default)
Which shell are you running NVM4W in?
PowerShell
User Permissions?
Standard Use, Non-Elevated
Is Developer Mode enabled?
No (Default)
Relevant log/console output
PS C:\> nvm use 20
exit status 1: 'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
exit status 1: 'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
PS C:\> nvm --version
1.1.11
PS C:\> $env:NVM_HOME
C:\Program Files\nvmDebug Output
PS C:\> nvm debug
<user> is not using admin or elevated rights.
PowerShell 7 (x64)
Windows Developer Mode: UNKNOWN (user cannot read registry)
NVM4W Version: 1.1.11
NVM4W Path: C:\Program Files\nvm\nvm.exe
NVM4W Settings: C:\Program Files\nvm\settings.txt
NVM_HOME: C:\Program Files\nvm
NVM_SYMLINK: C:\Program Files\nodejs
Node Installations: C:\Program Files\nvm
Active Node.js Version: v16.20.1
No problems detected.
Find help at https://github.com/coreybutler/nvm-windows/wiki/Common-IssuesAnything else?
No response
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Any update ?
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.