Run/Debug Configuration: NPM

Create: Run | Edit Configurations | | NPM

In this dialog, create configurations for running npm and Yarn scripts locally. "Locally" in the current context means that PyCharm itself starts Node.js installed on your computer, whereupon initiates script execution.

Learn more from npm, pnpm, and Yarn.

If a script launches an application in the development mode, you can modify the configuration, so it also starts a debugging session. To do that, go to the Browser / Live Edit tab and specify there the URL address at which the application will run. Learn more from Run and debug an Angular application with a single npm run/debug configuration, Run and debug a Vue.js application with a single npm run/debug configuration, and Run and debug a Vite application with a single npm run/debug configuration.

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.
To use Yarn, install it as described on the Yarn official website.

Configuration tab

Item	Description
package.json	In this field, specify the package.json file to run the scripts from. Choose the file from the drop-down list which shows all the package.json files detected in the current project or click and choose the required package.json in the dialog that opens.
Command	From this list, choose the npm CLI command to execute, by default `run-script` is selected. Learn more at npm documentation, under the section CLI Commands.
Scripts	From this drop-down list, choose the script to which the chosen command will be applied. The list contains all the scripts defined within the `scripts` property in the package.json file.
Arguments	In this field, specify the command-line arguments to execute a script with. Learn more from the npm official website.
Node interpreter	In this field, specify the Node.js interpreter to use. If you choose the Project alias, PyCharm will automatically use the project default interpreter from the Node interpreter field on the Node.js page . In most cases, PyCharm detects the project default interpreter and fills in the field itself. You can also choose another configured local or remote interpreter or click and configure a new one.
Node Options	In this field, type the Node.js-specific command-line options to be passed to the Node.js executable file. The acceptable options are: Use `--require coffeescript/register` to have CoffeeScript files compiled into JavaScript on the fly during run. This mode requires that the register.js file, which is a part of the `coffeescript` package, is located inside your project. Therefore, make sure you have the `coffeescript` package installed locally as described in Install the CoffeeScript compiler. Use `--inspect` or `--inspect-brk` parameter for Chrome Debugging Protocol support.
Package manager	In this field. specify the package manager to use. If you choose the `Project` alias, PyCharm 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.
Environment Variables	In this field, specify the environment variables for the Node.js executable file, if applicable. Click Browse to the right of the field and configure a list of variables in the Environment Variables dialog, that opens: To define a new variable, click and specify the variable name and value. To discard a variable definition, select it in the list and click . Click OK, when ready The definitions of variables are displayed in the Environment variables read-only field with semicolons as separators, for example: `NODE_PATH`: A `:`-separated list of directories prefixed to the module search path. `NODE_MODULE_CONTEXTS`: Set to 1 to load modules in their own global contexts. `NODE_DISABLE_COLORS`: Set to 1 to disable colors in the REPL.
Docker container settings	This read-only field shows port and volume bindings. Click to open the command preview. This field only appears when a Docker-based remote interpreter is selected.
Docker Compose	In this area, specify the commands and options to be passed to Docker Compose. Accept the default settings or click and specify custom ones, for example, custom Docker Compose flags, like `--rm` or `--service-ports`. Learn more from the Docker official website. Check the Command Preview. This field only appears when a remote interpreter via Docker Compose is selected.

Common settings

When you edit a run configuration (but not a run configuration template), you can specify the following options:

Item	Description
Name	Specify a name for the run configuration to quickly identify it among others when editing or running.
Allow multiple instances	Allow running multiple instances of this run configuration in parallel. By default, it is disabled, and when you start this configuration while another instance is still running, PyCharm suggests stopping the running instance and starting another one. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances.
Store as project file	Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project. By default, it is disabled, and PyCharm stores run configuration settings in .idea/workspace.xml.

Item

Description

Name

Specify a name for the run configuration to quickly identify it among others when editing or running.

Allow multiple instances

Allow running multiple instances of this run configuration in parallel.

By default, it is disabled, and when you start this configuration while another instance is still running, PyCharm suggests stopping the running instance and starting another one. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances.

Store as project file

Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project.

By default, it is disabled, and PyCharm stores run configuration settings in .idea/workspace.xml.

The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.

Item	Shortcut	Description
	`Alt+Insert`	Create a run/debug configuration.
	`Alt+Delete`	Delete the selected run/debug configuration. Note that you cannot delete default configurations.
	`Ctrl+D`	Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
		The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.
		Move into new folder / Create new folder. You can group run/debug configurations by placing them into folders. To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created. Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons. To remove grouping, select a folder and click .
		Click this button to sort configurations in the alphabetical order.

Before launch

In this area, you can specify tasks to be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.

Item	Shortcut	Description
	`Alt+Insert`	Click this icon to add one of the following available tasks: Launch Web Browser: select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser be launched with JavaScript debugger. Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in PyCharm yet, add its definition. For more information, refer to External tools and External Tools. Run Another Configuration: select to execute another run/debug configuration and wait until it finishes before starting the current configuration. If you want to run several configurations in parallel, use a compound run/debug configuration. Run File Watchers: select this option to have PyCharm apply all the currently active File Watchers. Run Remote External tool: adds a remote SSH external tool. Run Grunt task: select this option to run a Grunt task. In the Grunt task dialog that opens, specify the Gruntfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Grunt tool. Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the grunt-cli package. Run Gulp task: select this option to run a Gulp task. In the Gulp task dialog that opens, specify the Gulpfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool. Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package. Run npm Script: select this option to execute an npm script. In the NPM Script dialog that opens, specify the npm run/debug configuration settings. Compile TypeScript: select to run the built-in TypeScript compiler and thus make sure that all the changes you made to your TypeScript code are reflected in the generated JavaScript files. In the TypeScript Compile Settings dialog that opens, select or clear the Check errors checkbox to configure the behaviour of the compiler in case any errors are detected: If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start. If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched. Generate CoffeeScript Source Maps: select this option to generate the source maps for your CoffeeScript sources. In the dialog that opens, specify where your CoffeeScript source files are located.
	`Alt+Delete`	Click this icon to remove the selected task from the list.
	`Enter`	Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
	`Alt+Up` `Alt+Down`	Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list.
Show this page		Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window		By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration. Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing `Alt+4` or `Alt+5`.

Browser / Live Edit tab

Use the controls in this tab if you want the run/debug configuration to launch an application in the development mode and at the same time start a debugging session. Learn more from Run and debug an Angular application with a single npm run/debug configuration, Run and debug a Vue.js application with a single npm run/debug configuration, and Run and debug a Vite application with a single npm run/debug configuration.

Here you can also enable PyCharm to open the application in the browser.

Item	Description
Open browser	In this area, enable the application to open in the browser. After launch - select this checkbox to open the application on startup. From the list, select the browser to open the application in. If you are going to debug the application, select Google Chrome or another Chromium-based browser. URL - in this field, specify the URL address at which the application wil run. with JavaScript debugger - select this checkbox to start a debugging session at the same time as the application is launched in the development mode.