-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
nvm use
reports that the version was not installed or could not be found
#708
Comments
For instance, the `nvm use 12` will switch to the latest installed version of 12.*. Similarly, `nvm use 12.22` will switch to the latest installed version of 12.22.* Fixes coreybutler#708
Same here |
Any workaround while pull request isn't approved? |
@Rusinas the only workaround is to type the full version ;) so do |
Nope, typing the full version doesn't work either. I think I'm okay with 16 for now, but any chance your branch will be merged soon? |
same issue is happening for me. any idea when it will be fixed? |
Switch to installing node on Windows using NVS rather than NVM. NVS is not installed by default, so use Chocolatey to install it. NVM currently has two shortcomings that make it difficult to use in automation. "nvm install 16 && nvm use 16" doesn't work because "use" appears to need an exact patch version specified, which would involve parsing the output of "install" or of "list" since we only lock to major verisons. coreybutler/nvm-windows#708 "nvm use" and "nvm install" both give successful exit statuses even when they fail with an error message. This meant that when we did "nvm use 16", it failed because of the above bug, but the job kept on running and used the default version of Node installed in the image. Working around this would again involve parsing output. coreybutler/nvm-windows#738 In my testing, NVS appears to have neither of these problems. I had also considered installing Node directly via Chocolatey, but Chocolatey does not yet support installing particular versions unless the packager has appended the version number to the name. This also implies that likely only the latest major version gets updates.
I've been having this same issue, but when I use the full version I get the response: exit status 145: The directory is not empty. Any advice? |
I have the same problem here |
This is addressed in PR #709, which will be merged in an upcoming release. |
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. |
For instance, the `nvm use 12` will switch to the latest installed version of 12.*. Similarly, `nvm use 12.22` will switch to the latest installed version of 12.22.* Fixes coreybutler#708
I had the same issue, I resolve it by
Hope this solves your issue |
I met this issue when I installed 16.4.2 and tried to use it. |
i got some error in version 1.1.9 like " exit status 5: Access is denied." or "node vv12.22.12 (64-bit) is not installed or cannot be found" or " folder is not empty" and base of this instruction my problem solved on windows 10 x64 : |
I had the same problem and resolved it by running Git Bash as admin then using the |
I solved this problem by typing the full version. Example: nvm use 14.0.0. It works all fine now. |
This is now available in v1.1.10. |
@coreybutler Still happens to me in v1.1.11 Windows (via installer) |
@coreybutler |
You probably have a conflict in your |
Do you get an error running |
|
When I ran
|
I manually deleted all of the node version folders and I was now able to install and use node 16.20.0. This is very strange but I guess it's ok now. |
It looks like your prior installations weren't unpacked. I'm not sure how that happened because NVM4W unpacks the contents in a temp directory when it writes to the final location. It expects a file structure like this: I'm not sure why this occurred. If you have a mirror setup, it's possible the installers are in a different format. There are other users who have experienced similar symptoms, but it's not common and there is no clear reason why it's happening to some people and not others. If anyone else runs into this, please open a new issue. |
I had problems with version node 18 installed, but when I uninstalled 18, "npm use" and "npm list" worked correctly. |
I was facing the same issue with v20.4.0. Used nvm install v20.4.0 and it is working. |
I help running my cmd as admin |
Our CI automation reads
|
Issue:
How To Reproduce:
nvm install 16
Downloading node.js version 16.13.1 (64-bit)...
Extracting...
Complete
Installation complete. If you want to use this version, type
nvm use 16.13.1
nvm use 16
node vv16.13.1 (64-bit) is not installed or cannot be found.
Please notice the double v in front of the version.
nvm use 16.13.1
Now using node v16.13.1 (64-bit)
Expected Behavior:
nvm use
resolves the version properlyDesktop:
The text was updated successfully, but these errors were encountered: