Last active
March 12, 2025 13:37
-
Star
(763)
You must be signed in to star a gist -
Fork
(207)
You must be signed in to fork a gist
-
-
Save chranderson/b0a02781c232f170db634b40c97ff455 to your computer and use it in GitHub Desktop.
Useful NVM commands
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| // 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 |
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
