Run/Debug Configuration: Spy-js for Node.js
In this dialog box, create configurations for tracing Node.js applications using the Spy-js tool.
Getting access to the Run/Debug Configuration: Spy-js for Node.js dialog
- Download and install Node.js.
- Install and enable the Spy-js plugin. The plugin is not bundled with IntelliJ IDEA, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.
Spy-js for Node.js-specific configuration settings
|Node interpreter|| In this field, specify the Node.js interpreter to use, see Configuring a local Node.js interpreter for details. |
With Spy-js, it is recommended to use Node.js version 0.10.24 or higher.
To enable tracing ECMAScript 6 scripts, use Node.js version 0.11.13 or higher and specify
|Node parameters|| In this text box, 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 field shows the project root folder.|
|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 box, 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. |
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.
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
|Name||In this text box, 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|| 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
If the file-based format is used, the settings are stored in the
|Single instance only|
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.
|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.|
|Edit Templates||View and edit the default template for the selected run/debug configuration. The templates are used for newly created configurations.|
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 to be grouped, click , and specify the name for the folder. 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-and-drop or and buttons.
To remove grouping, select a folder and click .
|Sort configurations||Click this button to sort configurations in alphabetical order.|
When you select Templates in the tree view of the run configurations, you can adjust some settings that apply for all run debug configurations.
|Configurations available in Run Dashboard|| |
In this section you can create a list of run configurations available in the Run Dashboard — tool window that helps you execute and manage multiple run/debug configurations.
Note that the dashboard will only display those configuration types for which you have created one ore more configurations.
|Confirm rerun with process termination||The behavior of this checkbox depends on whether the Single instance only checkbox is selected for a particular run/debug configuration. |
|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.|
Before Launch options
In this area you can specify tasks that should be carried out before starting the selected run/debug configuration. The specified tasks are performed in the order they appear in the list.
|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|| |
Otherwise, 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.