nvm VS cross-env

The conventional way to manage versions in Node.js is through nvm. You add a .nvmrc file stating the version used to the root of your repository and then you can quickly switch to that version. The content of the file is simply the version you want:

npm (Node Package Manager) is a binary that comes with “node” (NodeJs). You can install node using nvm (https://github.com/nvm-sh/nvm).

> git clone https://github.com/nvm-sh/nvm.git > cd nvm

You can use Node Version Manager (NVM) for this purpose. https://github.com/nvm-sh/nvm. It lets you switch to different node versions via CLI. Hope it helps!

Node.js - Usando NVM

We are going to install Node via NVM so that we can easily change node versions and then we will use npm to install pm2.

Ah right, npm7 is dropped in node v16.11. You may want to use nvm and install node v16.10 to get npm7.

Here is link number 1 - Previous text "nvm"

I suggest try https://www.npmjs.com/package/cross-env

What is your OS ? windows ? you might need to set env variable the windows way or use something like cross-env https://github.com/kentcdodds/cross-env

cross-env: Run scripts that set and use environment variables across different platforms. We’ll use it to make our scripts compatible with both Unix and Windows OSes.

As a development dependency, we included cross-env, which makes it easy to have a single command for setting and using environment variables properly for the target platform.

cross-env

cross-env - Cross platform configuration

That uses https://www.npmjs.com/package/cross-env to set the production environment variable. It's useful so that it works on both Window and Linux.