CLion integrates with the npm, pnpm, Yarn, Yarn 2, and Yarn 3, so you can install, locate, update, and remove packages of reusable code from inside the IDE, in the built-in Terminal.
CLion also lets you run and debug npm, Yarn, and pnpm scripts. CLion parses package.json files, recognizing definitions of scripts, shows scripts in a tree view, and lets you navigate between a script in the tree and its definition in the package.json file. For more information, refer to npm, Yarn, and pnpm official websites.
CLion detects projects with Yarn workspaces and indexes all the dependencies that are listed in the package.json files of the workspaces but are located in the root node_modules folder.
Before you start
Download and install Node.js. Note that npm is also installed, so if you are going to use it, you are through with the preliminary steps.
With CLion, you can choose whether to use npm, Yarn, Yarn 2, or pnpm in a project.
By default, CLion suggests npm. However, if you open a project with a yarn.lock file and Yarn is installed on your computer, CLion automatically changes the package manager for this project to Yarn.
Accordingly, if you open a project with a pnpm-lock file and pnpm is installed on your computer, CLion automatically changes the package manager for this project to pnpm.
In the Settings dialog (CtrlAlt0S), go to Languages & Frameworks | Node.js. The Node.js page opens.
In the Package manager field, specify the package manager for your project.
Select npm, yarn, or pnpm to use the system default installation.
tip
CLion uses the npm, yarn, and pnpm aliases for the current system paths to these managers. If you choose another Node.js version, CLion also changes the npm aliased path to point to the npm version bundled with the selected Node.js version.
To use a custom installation of a package manager, click Select, and select the installation folder of the relevant package manager.
CLion automatically uses the chosen package manager when you select the Project alias from the Package manager list in the Run/Debug Configuration: NPM dialog. CLion also uses the path to the chosen package manager every time you invoke the Run 'npm install'/Run 'yarn install'/Run 'pnpm install' command or run an npm/Yarn/pnpm script. For more information, refer to Running and debugging scripts.
Set up Yarn 2 in your project
Make sure you have Yarn 1 installed globally and enable Yarn 2 in your project as described on the Yarn official website. Use the embedded TerminalAltF12 to type the commands.
In the Settings dialog (CtrlAlt0S), go to Languages & Frameworks | Node.js and select the path to the Yarn 2 package in your project from the Package manager list.
Set Yarn 1 or pnpm as the default CLion package manager
Open the Settings for New Projects dialog (File | Settings for New Projects) and go to Languages & Frameworks | Node.js.
On the Node.js and NPM page that opens, select yarn or pnpm from the Package manager list.
After that, CLion will suggest the selected package manager (Yarn or pnpm) as default every time you create a new project.
Edit package.json
CLion helps you handle your project dependencies in package.json files providing extensive coding assistance.
Code completion for package names.
Information on the latest available package version.
Information about the range of versions that can be installed through npm install <package>@<version> or yarn add <package>@<version>. `Note that running npm install or yarn install will install the latest available version from this range.
Press Ctrl and hover over the version to see the information in a tooltip. See the npm Official documentation for details about semantic versioning.
Code completion for previous package versions. When you press CtrlSpace or start typing a version different from the latest one, CLion displays a suggestion list with all the previous versions of the package.
Quick documentation look-up for packages.
tip
CLion also shows readme files for npm packages when you invoke documentation look-up from require or import statements.
Install and update packages
As you may know, npm can install packages both globally or as project dependencies or development dependencies, learn more from the npm official website.
pnpm also installs packages globally or as project dependencies or development dependencies, learn more from the pnpm official website.
With Yarn, you can install packages globally or as project dependencies. For more information, refer to Yarn official website.
In CLion, packages can be installed in the editor, from a package.json file, in the built-in TerminalAltF12, or on the Node.js page.
From package.json
Install your project dependencies
Click the Run 'npm install', Run 'yarn install', or Run 'pnpm install' link in the popup:
CLion shows this popup when the dependencies are not installed yet or when they have changed. If you close the popup or turn it off by choosing Don't ask again, you can still install the dependencies using the Run '<package_manager> install' action or in the built-in terminal.
If you have accidentally dismissed this notification and now want to get it back, press CtrlShift0A, start typing Enable notifications, and select Enable Notifications about Installing Dependencies from package.json from the list.
Alternatively, open the relevant package.json file in the editor or select it in the Project tool window and choose Run 'npm install' from the context menu.
Update your project dependencies
Click Run '<package manager> install' in the popup.
CLion shows this popup every time you open a project, update it from the version control, or edit a package.json.
CLion also runs an inspection that checks whether the packages from dependencies or devDependencies are installed and their versions match the specified range. If the inspection detects any mismatch, it suggests a quick-fix. To apply it, click the Run '<package manager> install' link.
CLion also detects packages for which later versions are available and provides a quick-fix when you hover over the package version.
Alternatively, press AltEnter and select Update <package> to the latest version from the list:
In the built-in Terminal
In the embedded Terminal (AltF12) , type one of the following commands:
For global installation:
npm install --global <package_name>
yarn global add <package_name>
pnpm --global add <package_name>
To install a package as a project dependency or a development dependency:
npm install --save <package_name> or npm install --save-dev <package_name>
yarn add <package_name> --dev
pnpm add --save-dev <package_name>
Install all dependencies listed in a package.json file
In the embedded Terminal (AltF12) , type one of the following commands:
npm install
yarn install
pnpm install
As a result you get all the dependencies listed in the package.json from the current folder. Learn more from Editing package.json.
note
For packages installed via Yarn 2, CLion shows yarn:package.json:< package name> instead of the actual path to a package. Note that this format is used only for presenting a package in the Settings dialog but not for specifying its location in your code or elsewhere.
As you write your code, the IDE highlights packages that are considered vulnerable, provides descriptions for them, and suggests fixes where available.
Gif
In the Problems tool window, you can view a list of detected vulnerable packages.
To solve package vulnerability problems in the editor, hover over the highlighted package in a package.json file. The popup tool window shows a description of the detected vulnerability.
To apply a quick-fix, click More actionsAltEnter and select the relevant suggestion.
To view vulnerable packages in the Problems tool window, click in the inspection widget.
The File tab of the Problems tool window lists all the vulnerable packages from the package.json that is open in the active editor tab. Each item is supplied with a description.
To solve a problem, select the vulnerable package in the list, click on the toolbar or press AltEnter, and then select the relevant suggestion.
The Vulnerable Dependencies tab lists all the vulnerable packages detected in your project.
To fix a problem, select the vulnerable package in the list, click the Copy safe version to clipboard link on the right-hand pane, and then paste the copied version to your package.json.
By default, package vulnerability check is enabled. To turn it off, open the Settings dialog (CtrlAlt0S), go to Editor | Inspection, and clear the checkboxes next to the relevant inspections under the Security node.
Run and debug scripts
You can launch npm, Yarn, or pnpm scripts from a package.json file in the editor, from a tree of scripts in the dedicated npm tool window, according to a dedicated run configuration, or automatically, as a start-up or a before-launch task.
The results of script execution are displayed in the Run tool window. The tool window shows the npm or Yarn script output, reports the errors occurred, lists the packages or plugins that have not been found, etc. The name of the last executed script is displayed on the title bar of the tool window.
Gif
If you launch a script debugging session, CLion opens the Debug tool window.
Gif
During a script debugging session, you can step through the script, stop and resume the script execution, examine it when suspended, run JavaScript code snippets in the Debugger Console, and so on.
Run and debug scripts from package.json
CLion lets you quickly launch single scripts from package.json files. To run or debug several scripts, use a run configuration or the npm tool window.
Open the package.json file in the editor, click in the gutter next to the script, and choose Run <script_name> or Debug <script_name> from the context menu.
You can also run a script by pressing CtrlShiftF10.
The script output is shown in the Run tool window.
The npm tool window opens when you select a package.json file in the Project tool window or open it in the editor and select Show npm Scripts from the context menu.
As soon as you invoke npm, pnpm, or Yarn, the tool starts building a tree of scripts defined within the scripts property of the package.json file on which it was invoked.
If you have several package.json files in your project, you can build a separate script tree for each of them and run scripts without dropping the previously built trees. Each tree is shown under a separate node.
Open the npm tool window if it is not opened yet
Select the required file in the Project tool window or open it in the editor and choose Show npm Scripts from the context menu.
The npm tool window opens showing the scripts tree built according to the selected or opened package.json file.
Build a tree of scripts in an already opened npm tool window
In the npm tool window, click on the toolbar and choose the required package.json file from the list. By default, CLion shows the package.json file in the root of your project.
If you have another package.json file, click Choose package.json and select the package.json file you need in the dialog that opens. CLion adds a new node with the path to the chosen package.json file on its title and builds a scripts tree under the new node.
Gif
Re-build a tree
Switch to the required node and click on the toolbar.
Gif
Sort the scripts in a tree by their names
Click on the toolbar, choose Sort by from the menu, and then choose Name.
By default, a tree shows the scripts in the order in which they are defined in package.json (option Definition order).
Gif
Run one script
Double-click the script.
Select the script in the tree and press Enter or choose Run <script name> from the context menu.
Gif
Debug one script
Select the script in the tree and choose Debug <script_name> from the context menu.
Use the multiselect mode: hold Shift (for adjacent items) or Ctrl (for non-adjacent items) keys and select the required scripts, then choose Run or Debug from the context menu of the selection.
Run and debug scripts by a run configuration
When you run or debug scripts from the editor or from the npm tool window, CLion automatically creates temporary run configurations. Besides using them, you can create and launch your own npm run configurations.
Create an NPM run/debug configuration
Go to Run | Edit Configurations. Alternatively, select Edit Configurations from the list on the toolbar.
In the Edit Configurations dialog that opens, click the Add button () on the toolbar and select npm from the list. The Run/Debug Configuration: npm dialog opens.
Specify the CLI command to execute, the scripts to run (use blank spaces as separators), and the location of the package.json file where these scripts are defined. Optionally, type the command-line arguments for executing the scripts.
Specify the Node.js interpreter to use.
If you choose the Project alias, CLion will automatically use the project default interpreter from the Node interpreter field on the Node.js page . In most cases, CLion detects the project default interpreter and fills in the field itself.
You can also choose another configured local interpreter or click and configure a new one.
Specify the package manager to use. If you choose the Project alias, CLion will use the default project package manager from the Node.js page. You can also choose the relevant package alias (npm or yarn) or specify an explicit path to a custom installation of a package manager.
If you are using a remote Node.js interpreter in a Docker container, check the port and volume bindings values in the Docker container settings field.
Press Ctrl twice or click on the Navigation bar. The Run Anything popup opens.
Type npm run or yarn run in the search field. As you type, CLion shows the matching scripts. Select the required one from the list and press Enter.
To view the command output in the Run tool window, press CtrlEnter, to show the output in the Debug tool window, press ShiftEnter.
Gif
Run scripts automatically on start-up
If you have some scripts that you run on a regular basis, you can add the corresponding run configurations to a list of startup tasks. The tasks will be executed automatically on the project start-up.
In the Settings dialog (CtrlAlt0S), go to Tools | Startup Tasks.
From the list, choose the required npm run configuration. The configuration is added to the list.
If no applicable configuration is available in the project, click and choose Edit Configurations. Then define a configuration with the required settings on the Run/Debug configuration page that opens. When you save the new configuration it is automatically added to the list of startup tasks.
Run scripts as before-launch tasks
Open the Run/debug configurations dialog dialog by choosing Run | Edit Configurations from the main menu, and select the required configuration from the list or create it anew by clicking and choosing the relevant run configuration type.
In the dialog that opens, click in the Before launch area and choose Run npm script from the list.
With CLion, you can edit package.json, install, update, and remove dependencies of a project in a Docker container just in the same way as you do it locally.
Make sure the Docker plugin is enabled in the settings. Press CtrlAlt0S to open the IDE settings and then select Plugins. Click the Installed tab. In the search field, type Docker. For more information about plugins, refer to Managing plugins.
in the inspection widget.
on the toolbar or press AltEnter, and then select the relevant suggestion.
in the gutter next to the script, and choose Run <script_name> or Debug <script_name> from the context menu.
on the toolbar and choose the required package.json file from the list. By default, CLion shows the package.json file in the root of your project.
on the toolbar. 
Gif
on the toolbar, choose Sort by from the menu, and then choose Name. 
Gif
and configure a new one.
or 
next to the list.
on the Navigation bar. The Run Anything popup opens.
Gif