| Item | Description | ||||||
|---|---|---|---|---|---|---|---|
| Path to Node |
In this field, specify the NodeJS installation home. Type the path to the NodeJS executable file manually,
or click the Browse button
and select the location in the dialog box, that opens.
If you have appointed one of the installations as default, the field displays the path to its executable file. | ||||||
| Node parameters | In this text box, type the NodeJS-specific command line options to be passed to the NodeJS executable file. The acceptable options are: | ||||||
| Path to Node App JS file |
In this field, specify the full path to the NodeJS file to start running or debugging from.
If you are going to debug CoffeeScript, specify the path to the generated JavaScript file with source maps. The file can be generate4d externally or through transpilation using file watchers. For more details, see Transpiling CoffeeScript to JavaScript. | ||||||
| Application parameters |
In this text box, type the NodeJS-specific arguments to be passed to the starting NodeJS application file
through the process.argv array.
| ||||||
| Working directory |
In this field, specify the location of the files referenced from the starting NodeJS application file, for example, includes.
If this file does not reference any other files, just leave the field empty.
Choose the folder from the drop-down list, or type the path manually, or click the Browse button
and select the location in the dialog box, that opens.
| ||||||
| Environment variables |
In this field, specify the environment variables for the NodeJS executable file, if applicable.
Click the Browse button to the right of the field and configure a list of variables
in the Environment Variables dialog box, that opens:
The definitions of variables are displayed in the Environment variables read-only field with semicolons as separators. The acceptable variables are:
| ||||||
| Run with CoffeeScript plugin | If this check box is selected, you can launch the CoffeeScript files directly, without previously transpiling them to JavaScript. | ||||||
| Path to coffee executable | Specify here the path to the executable file that launches the CoffeeScript transpiler. | ||||||
| CoffeeScript parameters | Specify here the parameters to be passed to CoffeeScript. |
Toolbar
| Item | Shortcut | Description |
|---|---|---|
| InsertInsert | Click this button to add new configuration to the list. |
| DeleteDelete | Click this button to remove the selected configuration from the list. |
| Ctrl+DCtrl+D | Click this button to create a copy of the selected configuration. |
| Edit defaults | Click this button to edit the default configuration templates. The defaults are used for the newly created configurations. |
or
| Alt+UpControl Up or Alt+DownControl Down | Use these buttons to move the selected configuration or group of configurations (folder) up and down in the list.
The order of configurations or folders in the list defines the order, in which configurations appear in the Run/Debug drop-down list on the main toolbar. |
| Use this button to create a new folder.
If one or more run/debug configurations have the focus, then the selected run/debug configurations 0 are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created. |
Common options
| Item | Description | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Name | In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations. | |||||||||||||||||||||
| Defaults | This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations. | |||||||||||||||||||||
| Temporary configurations limit | Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list. | |||||||||||||||||||||
| Share |
Select this check box to make the run/debug configuration available to other team members.
If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate xml file in the .idea\runConfigurations folder if the run/debug configuration is shared and in the .idea\workspace.xml file otherwise. If the file-based format is used, the settings are stored in the .ipr file for shared configurations or in the .iws file for the ones that are not shared. This check box is not available when editing the run/debug configuration defaults. | |||||||||||||||||||||
| Single instance only | If this check box is selected, this run/debug configuration cannot be launched more than once.
Every time a new run/debug configuration is launched, IntelliJ IDEA checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place. This make sense, when usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources. If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window. | |||||||||||||||||||||
| Before launch | Specify which tasks should be carried out before starting the run/debug configuration.
The specified tasks are performed in the order that they appear in the list.
|

framework.
and select the location in the dialog box, that opens.
and specify the variable name and value.
.
or
