CLion 2016.2 Help

Node.js and NPM

File | Settings | Languages&Frameworks | Node.js and NPM for Windows and Linux
CLion | Preferences | Languages&Frameworks | Node.js and NPM for OS X
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 CLion, 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, specify the local Node.js interpreter to use. Choose the interpreter from the drop-down list or click browseButton and choose the interpreter in the dialog box that opens.
VersionThis read-only field shows the current version of the runtime environment.
Code Assistance When developing a Node.js application it can be convenient to have code completion, reference resolution, validation, and debugging capabilities for Node core modules (fs, path, http, etc.). However, these modules are compiled into the Node.js binary. CLion provides the ability to configure these sources as a JavaScript library and associate it with your project.
  • If the Node.js core module sources are not set up, CLion displays a notification Node.js Core Library is not enabled with an Enable button. Click this button to have CLion configure Node.js Core sources automatically.

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

  • If the library is set up, CLion displays information about the currently configured version, the notification Node.js Core Library is enabled, and adds two buttons: the Disable button and the Usage scope button.
    • Click the Disable button to discard the configuration of the Node.js Core libraries in the current project.
    • Click the Usage scope button to associate the desired directories with libraries.
Packages 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.
  • 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 add 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 check box and type -g in the Options text box. Global installation makes the package available at the CLion level so it can be used in any CLion 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.

See Also

Last modified: 20 July 2016