Run/Debug Configuration: Spy-js
In this dialog box, create configurations for tracing Web applications using the Spy-js tool.
On this page:
- Getting Access to the Run/Debug Configuration: Spy-js Dialog Box
- Spy-js-Specific Configuration Settings
- Common Options
Getting Access to the Run/Debug Configuration: Spy-js Dialog Box
- Download and install Node.js because it is used by the Spy-js trace server.
- Make sure the Spy-js plugin is enabled. The plugin is bundled with WebStorm and activated by default. If not, enable it on the Plugins page of the Settings dialog box as described in Enabling and Disabling Plugins.
Spy-js-Specific Configuration Settings
In this field,
specify the NodeJS installation home. Type the path to the NodeJS executable file manually,
or click the button
and select the location in the dialog box, that opens.
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||
|Alt+Insert||Click this button to add a new configuration to the list.|
|Alt+Delete||Click this button to remove the selected configuration from the list.|
|Ctrl+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 newly created configurations.|
|or||Alt+Up or Alt+Down||Use these buttons to move the selected configuration or 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.
|Sort configurations||Click this button to sort configurations in alphabetical order.|
|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.
The shared run/debug configurations are kept in separate xml files under
This check box is not available when editing the run/debug configuration defaults.
|Before launch||Specify which tasks must be performed before applying the run/debug configuration.
The specified tasks are performed in the order they appear in the list.