g VS nvm

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 really like g: https://github.com/stefanmaric/g It’s simple, fast to use, and reliable.

If you are using a Unix based system you can use: https://github.com/stefanmaric/g I use it daily and works like charm, I only had some problems using `godoc` but it is solveble if you set the GOPATH to the go location and not the g installation directory

Don't use Brew for Go! Brew is great for a lot of things but but not for Go installation. So far this is the best Go version manager i've found. It can be nice to have different versions easily available. https://github.com/stefanmaric/g

I used this, easy and stable https://github.com/stefanmaric/g

Whatever the language, I find that using a version manager reduces stress considerably. This is the one I use, but there are others: https://github.com/stefanmaric/g

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.