IntelliJ IDEA 2017.3 Help

Node.js and NPM

File | Settings | Languages and Frameworks | Node.js and NPM for Windows and Linux
IntelliJ IDEA | Preferences | Languages and Frameworks | Node.js and NPM for macOS
Ctrl+Alt+S settings

This page appears in the Settings dialog box, when the Node.js plugin is enabled. The plugin is not bundled with IntelliJ IDEA, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.

ItemDescription
Node interpreter In this field, choose the interpreter from the drop-down list or from the dialog that opens when you click browseButton.

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.

VersionThis read-only field shows the current version of the runtime environment.
Coding Assistance In this area, click Enable to configure the Node.js Core module sources as a JavaScript library and associate it with your project. As a result, IntelliJ IDEA provides code completion, reference resolution, validation, and debugging capabilities for fs, path, http, and other core modules that are compiled into the Node.js binary.

When the configuration is completed, IntelliJ IDEA displays information about the currently configured version, the notification Node.js Core Library is enabled, and adds the Disable and the Usage scope buttons.

Optionally
Configure the scope in which the Node.js Core sources are treated as libraries:

  1. Click Usage scope. The Usage Scope dialog opens.
  2. Click the relevant directories, and for each of them select the newly configured Node.js Core library from the list.

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.
  • Package: this read-only field shows the name of a package, exactly as it should be referenced if you were installing it in the command line mode.
  • Version: this read-only field shows the version of the package installed on your computer.
  • Latest: this read-only field shows the latest released version of the package. If a package is not up-to-date, it is marked with a blue arrow arrow right.
  • Click new to have a new package installed. In the Available Packages dialog box that opens, select the relevant package. To have the package installed globally, select the Options checkbox and type -g in the Options text box. Global installation makes the package available at the IntelliJ IDEA level so it can be used in any IntelliJ IDEA project. Click Install Package when ready.
  • Click delete to have the selected package removed.
  • Click arrowUp to have the current version of the selected package replaced with the latest released version. The button is enabled only when the selected project is not up-to-date.
Last modified: 6 March 2018
MarkdownOSGi

See Also

Language and Framework-Specific Guidelines: