HomeBrew VS nvm

I recommend installing homebrew so you can install/update applications from the command line.

Brew & macports have libvirt & virt-manager that are used to manage qemu via GUI.

To install the Homebrew package manager, see: link

In case you're not not aware of it, virtually all devs on mac use homebrew. I slide nearly seamlessly between WSL and mac depending on whether I feel like using my desktop or laptop at the moment. The differences largely boil down to whether I apt install or brew install things. And as much as I'm loathe to admit it, vscode + vim plugin these days gives emacs + evil a pretty good run for the money when it comes to extensible IDEs.

There’s no practical difference between trusting that a popular GitHub account hasn’t been compromised (see: https://brew.sh) and your distro or other package managers haven’t been compromised when it comes to machine setup. If security is that much of a priority you run your own mirrors and don’t pull from public repositories/registries. IME you want to do that for availability anyways if this is for work. Nothing worse than a failed build for a hot-fix because some package registry is temporarily offline.

Others have offered solutions, but for future reference the actual Terminal commands that failed would be useful; "File not found" sounds like a path error, "Command not found" sounds fixable via Homebrew or Macports

TL;DR, about the section that states software from other UNIX-like OSes is hard to port to MacOS, how about homebrew and macports?

First, you’ll want to install some base dependencies for your operating system. We will use brew 27 for this. If you don’t have brew installed you can do so by running:

Prerequisites: Ensure you have Homebrew installed on your computer. It is a package that enables you to install various applications not provided by Apple.

Get it with Homebrew:

Instalación de Node Version Manager (NVM)

Note that for the purpose of this tutorial, I’m using node version 16.13.0 and npm version 8.1.0. You can make use of Node Version Manager (NVM) to manage and use this exact version of node and npm. Follow this guide for a step-by-step tutorial on how to use NVM.

NodeJS - recommended way to install is nvm

Check Node Version Manager, such as https://github.com/nvm-sh/nvm

There are multiple issues about this topic https://github.com/nvm-sh/nvm/issues/2724

GitHub - nvm-sh/nvm: Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions

I don't know if you tried it already, but there's nvm for that (or Volta if we're being blazingly fast 🚀🚀🚀)

Install nvm: curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.2/install.sh | bash

Node.js: Ensure that you have the NVM tool installed on your local development environment. Also, take note to install Node version above v14 via the 'nvm install' command.