goenv VS nvm

What does this have that https://github.com/syndbg/goenv doesn't?

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.

There are Go version managers (like goenv) that let you install multiple versions of go without polluting global PATH/GOBIN/GOPATH.

I use GoEnv. I hate that I have to do it, but I have valid (if annoying) reasons. I'd rather just keep the most recent version installed.

https://github.com/syndbg/goenv is a shell implementation that uses a shim to make calls to go. drewgonzales360s version will symlink to whichever version of Go a user chooses.

I am surprised I only saw one comment for goenv. This is literally the easiest way for all languages that have something similar (Python, Ruby, Go, Terraform, etc.). You need to uninstall all your go binaries, then install goenv, and all you have to do is to put in a project a .go-version file containing a single line with the version you need. The files are searched by the tool in a hierarchical order: if in the current directory where go is ran, no .go-version file is found, the tool will look up one directory, if there’s no ../.go-version will try again and so on. Let’s say in the end you will want to run the same go-version across all your projects, all you have to do is to find the first common parent directory and put a .go-version file in there, or simply just put a file in the root directory (/.go-version) or just use the global file (~/.goenv/version).

Not really answering your question but if you want to use Go 1.18 already there's a Go versions management tool called goenv that already has Go 1.18 and you can use already.

Kubebuilder doesn’t support Go 1.17, so we need to install Go 1.16. I decided to use goenv to manager Go versions.

i use goenv. works like a charm.

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.

in order to install Node on your Linux environment. Next up is NVM. I suggest going to https://github.com/nvm-sh/nvm and getting the latest install script from there. The current download is:

You can find the script to install nvm on their GitHub repository.