To get access to this dialog box:
- Download and install Node.js because it is used by the Spy-js trace server.
Install and enable the Spy-js repository plugin.
The plugin is not bundled with IntelliJ IDEA, but it is available from the JetBrains plugin repository. Once enabled, the plugin is available at the IDE level, that is, you can use it in all your IntelliJ IDEA projects. See Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins for details.
In this dialog box, create configurations for debugging using the Spy-js tool.
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.
With Spy-js, it is recommended to use Node.js version 0.10.24 or higher.
|Trace server port||
In this spin box, specify the port on which Spy-js will act as a proxy server.
This port number must be the same as your system proxy port.
If the Automatically configure system proxy check box is selected, the specified port number is automatically set for the system proxy server.
Otherwise you will have to specify the value of the field in the system proxy settings manually.
The trace server port is filled in automatically. To avoid port conflicts, it is recommended that you accept the suggested value and keep the Automatically configure system proxy check box selected.
In this drop-down list, specify the way to configure a tracing session.
|URL to trace||In this field, specify the URL address of the Web page to capture events on. By default, the field is empty. This means that Spy-js captures events on all the currently opened Web pages. If you want to restrict the tracing to a certain page, specify its URL address. Type the address manually or choose it from the drop-down list, if it has been once specified in the configuration.|
|Automatically configure system proxy||
|or or or or||Click this button to add new configuration to the list.|
|Click this button to remove the selected configuration from the list.|
|, or||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||or or or||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 are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or buttons.
|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.|
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.
|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.