Node.js and NPM
This page appears in the Settings dialog, when the Node.js plugin is enabled. The plugin is not bundled with JetBrains Rider, but it can be installed from the JetBrains plugin repository as described in Managing plugins.
In this field, specify the default Node.js interpreter for the current project. JetBrains Rider will automatically use it every time you select the
Select a configured interpreter from the list or click and configure a new one in the dialog that opens as described in Configuring a local Node.js interpreter. If you select node, the system Node.js version is used.
Here you can choose or configure only a local Node.js interpreter, that is, a Node.js installed on your computer, or a Node.js on Windows Subsystem for Linux, see Configuring a local Node.js interpreter and Using Node.js on Windows Subsystem for Linux for details.
Remote interpreters are configured in the Configure Node.js Remote Interpreter dialog accessible from the Run/Debug Configuration: Node.js. See Node.js with Docker, Node.js via SFTP, Node.js via SSH, and Node.js with Vagrant for details.
This read-only field shows the current version of Node.js.
Coding assistance for Node.js
If you need code completion for Node.js APIs only in some parts of your project, you can configure that using the Manage scopes link. In the Usage dialog that opens, click the relevant directories and for each of them select the configured Node.js Core library from the list. Learn more from Configuring the scope of a library.
JetBrains Rider uses the
By default, JetBrains Rider suggests npm. However if you open a project with a yarn.lock file and Yarn is installed on your machine, JetBrains Rider automatically changes the package manager for this project to Yarn. You can also set Yarn as default JetBrains Rider package manager.
| The Packages area shows a list of all the NPM-dependent packages that are currently installed on your computer. |