Run/Debug Configuration: Spy-js for Node.js
In this dialog, create configurations for tracing Node.js applications using the Spy-js tool.
Before you start
Download and install Node.js.
Install the NodeJS plugin on the Plugins page as described in Managing plugins.
Spy-js for Node.js-specific configuration settings
Item | Description |
---|---|
Node interpreter | In this field, specify the Node.js interpreter to use. This can be a local Node.js interpreter or a Node.js on Windows Subsystem for Linux. With Spy-js, it is recommended that you use Node.js version 0.10.24 or later. To enable tracing ECMAScript 6 scripts, use Node.js version 0.11.13 or later and specify |
Node parameters | In this field, type the Node.js-specific command line options to be passed to the NodeJS executable file. For example, to enable tracing ECMAScript 6 scripts, specify |
Working directory | In this field, specify the working directory of the application. By default, the Working directory field shows the project root folder. To change this predefined setting, specify the path to the desired folder or choose a previously used folder from the list. |
JavaScript file | In this field, specify the path to the main file of the application that starts it (for example, bin/www for Node.js Express applications). If you are going to trace CoffeeScript, specify the path to the generated JavaScript file. The file can be generated externally or through compilation using file watchers. For more details, see Debugging CoffeeScript. |
Application parameters | In this text box, type the Node.js-specific arguments to be passed to the application on start through the process.argv array. |
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:
The definitions of variables are displayed in the Environment variables read-only field with semicolons as separators. The acceptable variables are:
|
Configuration file | From this drop-down list, choose the file with the configuration settings to apply to the tracing session. A configuration file is a JavaScript file with the extension .js or .conf.js that contains valid JavaScript code that meets the Spy-js configuration requirements. If IntelliJ IDEA detects files with the extension .conf.js in the project, these files are displayed in the drop-down list. Type the path to the configuration file manually or click Browse and choose the location in the dialog box that opens. Once specified, a configuration file is added to the drop-down list so you can get if next time from the list instead of specifying the path. |
Common
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Item | Description |
---|---|
Name | In this field, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example, from the Run popup Shift+Alt+F10. |
Share through VCS | Select this checkbox to put the run/debug configuration under version control and make it 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, or 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 otherwise. |
Toolbar
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. | ||
View and edit the template (that is, the default settings) for the selected run/debug configuration. The templates are displayed under the Templates node and used for newly created configurations. | ||
/ | Alt+Up/Alt+Down | Move the selected run/debug configuration up and down in the list. The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration. Default templates of run/debug configurations are always sorted alphabetically. |
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 that must 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:
| |
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 isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5. |