nvs VS fnm

There is also node version switcher (nvs) https://github.com/jasongin/nvs which I found better then nvm if you dont want to go the full wsl route.

nvm can only be used in projects for macOS and Linux users. If you are Windows users, you can use nvm-windows, nodist or nvs.

nvs

Its been awhile since I have used nvm I switched to using this https://github.com/jasongin/nvs and haven't really had many issues with needing to reinstall packages when switching between node version.

I use nvs (https://github.com/jasongin/nvs). I'm sure nvm is good too, but I really like the menu you get when you run it without any arguments.. Also nvs has a Windows version, whereas nvm is POSIX OSes only.

I've run export NVS_HOME="$HOME/.nvs" and git clone https://github.com/jasongin/nvs "$NVS_HOME" but am running into problem when trying to run . "$NVS_HOME/nvs.sh" install.

Download the NVS msi file here (windows installer), then install it the same way as you install other windows applications.

nvs has been working pretty flawlessly for me.

Install nodejs: (I highly recommend using a node version manager like fnm) and to install a recent node version (current long term support is 16+)

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.

I switched from nvm to fnm a few years ago and have never looked back. Zero performance issues and it supports .nvmrc files.

https://github.com/Schniz/fnm

Are you using some kind of node version manager like fnm?

If it's your terminal that's slow in general and not neovim specifically I found that switching from nvm to fnm for managing node significantly faster at starting up my shell. I don't know whether this is what your issue is but I thought I'd share it regardless. https://github.com/Schniz/fnm

fnm is a fast and simple Node.js version manager. It's really easy to use and is much faster than nvm.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.

Install something like Fast Node Manager from https://github.com/Schniz/fnm and install your Node from there. I work in the software field and tend to use the LTS releases for the TypeScript/React projects I work on.

fnm!

You’ll need pnpm and Node.js installed on your machine + some tool for switching node versions (e.g. fnm or nvm will work fine);