awesome-mac VS nvm

A large number of extremely talented engineers might beg to differ. Everything you listed as an issue has a solution. Like any operating system, you have to spend the time to learn the intricacies of how it works and to customize it to your liking. For me, must haves are Alfred to replace spotlight, my dotfiles which change a ton of defaults in various apps like finder, the dock, etc, setup key repeat, iterm2 colors and profile, etc. divvy and magnet for window management. Caffeine to prevent sleep. Stats open source menu monitors to replace istatmenus

I’m sure there are newer equivalents to what I’ve listed. I’ve been using those programs for years.

Some jumping off points

https://github.com/jaywcjlove/awesome-mac

https://formulae.brew.sh/analytics/cask-install/30d/

Have a look at these lists for more of the things you are looking for: https://github.com/jaywcjlove/awesome-mac

I guess the awesome Mac list is a solid place to start generally speaking, since there are a lot of apps of all kinds of use cases in there. Personally, I especially love - Raycast (replacement for spotlight, check out Alfred as well) - Bartender (to tidy up the menu bar) - AltTab (gives you a Windows like app switcher) - Rectangle (windows like window management) - purepaste (let’s you paste text without formatting)

I always reference this great repo: https://github.com/jaywcjlove/awesome-mac

nvm - Node version manager

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.