GVM VS nvm

However this is still a neat script OP! I was looking for something like this when installing Go for the first time and was contemplating between goenv, gvm, and asdf before settling on brew.

I'd recommend using something like gvm: https://github.com/moovweb/gvm

Ah neat. For ref: https://github.com/moovweb/gvm. Not sure how I never saw that one. I guess I just probably googled "update golang bash github" at some point a few years ago and went with it.

I use the Go Version Manager. It is really easy to use and you can manage as many versions as you want: https://github.com/moovweb/gvm

Checkout out official GVM repo for more here.

We can use the gvm Go version manager to use versioned installation which is a tool that provides an interface to manage Go versions.

I've been using gvm for a while now to manage my Go versions. It's absolutely amazing, however, it's always lacked the ability to automatically create Go installations per repo like RVM does with .ruby_version.

what's new/different from all others Go version managers like https://github.com/moovweb/gvm for instance ?

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.