nvs VS nvm

There is also node version switcher (nvs) https://github.com/jasongin/nvs which I found better then nvm if you dont want to go the full wsl route.

nvm can only be used in projects for macOS and Linux users. If you are Windows users, you can use nvm-windows, nodist or nvs.

nvs

Its been awhile since I have used nvm I switched to using this https://github.com/jasongin/nvs and haven't really had many issues with needing to reinstall packages when switching between node version.

I use nvs (https://github.com/jasongin/nvs). I'm sure nvm is good too, but I really like the menu you get when you run it without any arguments.. Also nvs has a Windows version, whereas nvm is POSIX OSes only.

I've run export NVS_HOME="$HOME/.nvs" and git clone https://github.com/jasongin/nvs "$NVS_HOME" but am running into problem when trying to run . "$NVS_HOME/nvs.sh" install.

Download the NVS msi file here (windows installer), then install it the same way as you install other windows applications.

nvs has been working pretty flawlessly for me.

Node.js + Nvm - runtime for javascript without a browser

Install Node.js if it hasn't been installed. There are several ways to install Node.js. You may download the installer from the official website, or install it with tools like NVM. After installation, run this command to verify its installation.

Our server also needs Node.js to run our app. We could install the binary directly, but I prefer to use a tool called NVM, which allows us to easily manage Node versions. We can install it with this command:

By setting up your environment in isolation, you can prevent yourself from a lot of issues when experimenting with code. It makes your code behave more predictable due to the defined state of the runtime environment you are working with. This article should provide you with enough information to get started, but obviously, there is a lot more power embedded in NVM, Virtual Environment and RBEnv. So make sure to check their documentation.

I highly recommend setting up nodejs with a version manager, nvm was and still is a popular option, however, I now recommend and have been using fnm, a simpler and faster alternative to manage my nodejs versions.

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).

I usually develop on Windows so I installed NVM for Windows from here, but if you’re on other OS I’m sure you can find a version that supports it, probably this is the answer.

This was a very quick introduction to how I setup NodeJS on my environment using nvm. If you have any questions please refer to the official documentation or contact me via my Social Links.

Source: Can this be used to create/download npm as a standalone executable? #3237.