I used this approach on a project where the project could not even install packages if you had an incorrect node version. I used both ways, just because I had two projects with different requirements. It allows you to verify the node version via CLI (Command Line Interface) or programmatically. To verify the node version per JavaScript project, I found this npm package check-node-version.

Similar (not identical) to nvm, but for Windows. I needed a windows version, and the nvm Readme.md pointed me to nvm-windows (Download nvm-setup.zip). Nvm is a version manager for node.js, designed to be installed per-user, and invoked per-shell. To address the issue of running multiple versions of node on one machine, use nvm (Node Version Manager). My mission is clear, let the games begin… Solution nvm

This is because one of the packages in our project has a dependency on a specific node version.Īnother challenge was that I should still be able to work on multiple projects, each with their own node version dependency.

I recently had a situation where I needed to make sure the correct version of node is installed before one runs npm install.

Check node version mac