Node.js and NPM for Windows and Linux
Ctrl+Alt+S for macOS
Before you start, make sure the Node.js repository plugin is installed as described in Manage plugins.
In this field, specify the default Node.js interpreter for the current project. CLion will automatically use it every time you select the
Project alias from Node Interpreter lists when creating run/debug configurations or configuring Node.js-dependent tools, for example, Prettier or ESLint.
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. If you select node, the system Node.js version is used.
|Version||This read-only field shows the current version of Node.js.|
| Package manager |
In this field, choose the package manager (npm or Yarn) for the current project.
CLion uses the
yarn 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, see Configuring a package manager for a project for details.
By default, CLion suggests npm. However if you open a project with a yarn.lock file and Yarn is installed on your machine, CLion automatically changes the package manager for this project to Yarn. You can also set Yarn 1 as default CLion package manager.
| Packages || 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 .
Click to have a new package installed. In the Available Packages dialog that opens, select the relevant package. To have the package installed globally, select the Options checkbox and type
-g in the Options field. 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 to have the selected package removed.
Click 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: 14 May 2020