If you want to switch among several Node.js installations, you need to configure Node.js as a local interpreter.
To run a Node.js application remotely, configure it as a remote interpreter. See Node.js with Docker, Node.js via SFTP, Node.js via SSH, and Node.js with Vagrant for details.
Configuring a local Node.js interpreter
On the Node.js and NPM page, that opens, click next to the Node Interpreter list.
In the Node.js Interpreters dialog that opens with a list of all the currently configured interpreters, click on the toolbar. In the dialog that opens, choose Add Local from the context menu and choose the local installation of Node.js, then click OK. You return to the Node.js Interpreters dialog where the Node interpreter read-only field shows the path to the chosen interpreter.
In the Package manager field, choose the package manager (npm or Yarn) to use in the current project, see Configuring a package manager for a project for details.
When you click OK, you return to the Node.js and NPM page where the Node interpreter field shows the new interpreter.
Using a system Node.js version
With JetBrains Rider, you can set the default system node alias as your project’s Node.js version. This means that if you install a new node version and make it the default in your system, all the tools and run configurations in JetBrains Rider where this system alias is specified in the Node.js interpreter field will use this newer version.