Node.js and NPM
This page appears in the Settings dialog box, 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 Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.
|Node interpreter|| In this field, choose the interpreter from the drop-down list or from the dialog that opens when you click . |
The term local Node.js interpreter denotes a Node.js installation on your computer. The term remote Node.js interpreter denotes a Node.js installation on a remote host or in a virtual environment set up in a Vagrant instance. Here you can choose or configure only a local interpreter. Remote interpreters are configured in the Configure Node.js Remote Interpreter Dialog dialog which can be accessed only from the Run/Debug Configuration: Node.js dialog. See Configuring remote Node.js interpreters for details.
|Version||This read-only field shows the current version of the runtime environment.|
When the configuration is completed, JetBrains Rider displays information about the currently configured version, the notification Node.js Core Library is enabled, and adds the Disable and the Usage scope buttons.
|Packages|| A number of tools are started through Node.js, for example, the CoffeeScript, TypeScript, and Less compilers, YUI, UglifyJS, and Closure compressors, Karma test runner, Grunt task runner, etc. The Node Package Manager (npm) is the easiest way to install these tools, the more so that you have to install Node.js anyway. The Packages area shows a list of all the NPM-dependent packages that are currently installed on your computer. |