-
Star
(814)
You must be signed in to star a gist -
Fork
(215)
You must be signed in to fork a gist
-
-
Save chranderson/b0a02781c232f170db634b40c97ff455 to your computer and use it in GitHub Desktop.
| // check version | |
| node -v || node --version | |
| // list locally installed versions of node | |
| nvm ls | |
| // list remove available versions of node | |
| nvm ls-remote | |
| // install specific version of node | |
| nvm install 18.16.1 | |
| // set default version of node | |
| nvm alias default 18.16.1 | |
| // switch version of node | |
| nvm use 20.5.1 | |
| // install latest LTS version of node (Long Term Support) | |
| nvm install --lts | |
| // install latest stable version of node | |
| nvm install stable |
Thank you 🙏
very use full, thank you
nvm alias default 18.19.0 command is not changing the default node version on wsl.
Is this version installed on your machine?
Check your default node version using "nvm alias default"
nvm -v is 0.39.7. I have installed node version 14 and v18 via nvm. The nvm alias default command does not change the node version and only defaults to v14. However, the command nvm use default 18.19.0 is working but when restarting WSL it falls back to v14.21.3.
nvm -vis0.39.7. I have installed node version 14 and v18 via nvm. Thenvm alias defaultcommand does not change the node version and only defaults to v14. However, the commandnvm use default 18.19.0is working but when restarting WSL it falls back tov14.21.3.
Try command which node.
it gives you the path of the node binary currently active.
Check that ".nvm" is present on the path.
This is mine
nvm is present in which node command.
From the screenshot your machine load node 18 and not node14, so it seem that is resolved. Is it the case ??
It changes the node version but after closing the terminal or vs code, it reverts to node v14. The nvm alias default command is not working on WSL.
It changes the node version but after closing the terminal or vs code, it reverts to node v14. The
nvm alias defaultcommand is not working on WSL.
You don't have current alias. Maybe is this ...
Try this
# create alias named "current" that points to "default" aliased version
nvm alias current default
`nvm ls-remote` is not supporting from my side
they are suggesting to use `nvm ls available` or `nvm list available`
helping with more quick disk space reclaiming
On macOS
nvm uninstall v15.8.0
leaves 11.2 GB associated for that version in $HOME/.nvm/.cache/src
nvm cache clear
now that 11.2 GB is re-claimed (the current nvm node version is still intact in that directory). Didn't see any other earlier mention of cache here.
Explore a comprehensive list of NVM commands by clicking on the text below. -
