JavaScript Runtime
Preferred runtime
In this area, choose the runtime to use. The set of available runtimes depends on the plugins installed.
Package manager
In this field, choose the package manager (npm, Yarn, pnpm, bun) for the current project.
JetBrains Rider uses the npm, yarn, pnpm, and bun aliases for the current system paths to these managers. To use a custom installation, click Select, and select the installation folder of the relevant package manager. For more information, refer to Configuring a package manager for a project.
By default, JetBrains Rider suggests npm. However, if you open a project with a yarn.lock file and Yarn is installed on your computer, JetBrains Rider automatically changes the package manager for this project to Yarn.
Accordingly, if you open a project with a pnpm-lock file and pnpm is installed on your computer, JetBrains Rider automatically changes the package manager for this project to pnpm.
You can also set Yarn 1 or pnpm as default JetBrains Rider package manager.
Node.js
In this area, specify the Node.js runtime to use in your project and enable Node.js-specific coding assistance.
Node.js runtime
In this field, specify the default Node.js runtime for the current project. JetBrains Rider automatically uses it every time you select the Project alias from Node runtime lists, for example, when creating run/debug configurations.
Select a configured runtime from the list or click 
and configure a new one in the dialog that opens as described in Configuring a local Node.js runtime. If you select node, the system Node.js version is used.
You can select or configure a runtime of one of the following types:
Local interpreter — a Node.js installed on your computer. Learn more from Configuring a local Node.js runtime.
Node.js on Windows Subsystem for Linux, learn more from Using Node.js on Windows Subsystem for Linux.
Remote interpreter — a Node.js on a remote host or in a virtual environment. Learn more from Node.js with Docker, Node.js via SSH, and Node.js with Vagrant.
Version
This read-only field shows the version of the selected Node.js.
The following Node.js versions are supported in JetBrains Rider 2023.3 and later:
Node.js 22 - the Active Long Term Supported (LTS) version
Node.js 24 - the current version
Learn more from Supported Node.js versions
Coding assistance for Node.js
Select this checkbox to configure the Node.js Core module sources as a JavaScript library and associate it with your project. As a result, JetBrains Rider provides code completion, reference resolution, validation, and debugging capabilities for fs, path, http, and other parts of Node.js that are compiled into the Node.js binary.
When the configuration is completed, JetBrains Rider displays information about the currently configured version.
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.
Bun
In this area, specify the path to the Bun executable file.
The path to the Bun executable file defaults to your PATH environment variable, so if you leave the Bun field empty, the debugger attempts to detect the Bun executable file automatically.