install VS nvm

https://github.com/homebrew/install#uninstall-homebrew

Beyond what I've already said, I would refer you to look at how, e.g. Homebrew install.sh (and other repos in that project) handle a comparable setup. You can see a lot of what I have been flagging in there: tests, functions, comments, not making permanent changes outside remit, etc.

I was going to say that recent installs have switched to /opt/Homebrew, but while digging up supporting evidence I noticed that they bizarrely only do that for arm64 installs: https://github.com/Homebrew/install/blob/master/install.sh#L...

In comparison, Homebrew offers both an official install and uninstall script: https://github.com/Homebrew/install

this commit drops support for mavericks https://github.com/Homebrew/install/commit/4016e8675278dc7d5633179caf5507020091762b

The quick way to remove brew is literally on the website to install & uninstall brew: https://github.com/homebrew/install#uninstall-homebrew - if you plan to install/un/reinstall, it’s probably better to grab the actual scripts in those commands, but whatever.

Assuming you're using this? https://github.com/Homebrew

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.