WebStorm uses the npm, yarn, and pnpm aliases for the current system paths to these managers. In this field, choose the package manager (npm, Yarn, or pnpm) for the current project. Learn more from Configuring the scope of a library. 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. 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. When the configuration is completed, WebStorm displays information about the currently configured version. As a result, WebStorm 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. Select this checkbox to configure the Node.js Core module sources as a JavaScript library and associate it with your project.

This read-only field shows the current version of Node.js. See Node.js with Docker, Node.js via SSH, and Node.js with Vagrant for details. Remote interpreters are configured in the Configure Node.js Remote Interpreter dialog accessible from the Run/Debug Configuration: Node.js. 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. If you select node, the system Node.js version is used. 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. WebStorm automatically uses it every time you select the Project alias from Node Interpreter lists, for example, when creating run/debug configurations. In this field, specify the default Node.js interpreter for the current project.

Download node js ide jetbrains