Node.js and NPM
The plugin is bundled with WebStorm and activated by default. If it is not, enable it as described in Enabling and Disabling Plugins.
In this field,
specify the local Node.js interpreter to use.
Choose the interpreter from the drop-down list or click and choose the interpreter in the dialog box that opens.
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. On the Node.js and NPM page, you can specify only local interpreters. 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 Node.js Interpreters for details.
|Version||This read-only field shows the current version of the runtime environment.|
When developing a Node.js application it can be convenient to have code completion, reference resolution, validation, and debugging capabilities for Node core modules (|
If necessary, configure the scope in which the Node.js Core sources are treated as libraries. Click the Usage scope button, and in the Usage Scope dialog box that opens, click the desired directories, and from the drop-down list select the newly configured Node.js core module sources library.
A number of tools are started through Node.js, for example, the CoffeeScript, TypeScript,
and Less transpilers, 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.