WebStorm 2016.1 Help

Configuring JavaScript Debugger

Debugging JavaScript in WebStorm is supported through the JavaScript Debugger. The plugin is bundled with WebStorm and activated by default. If the plugin is not activated, enable it on the Plugins page of the Settings / Preferences Dialog as described in Enabling and Disabling Plugins.

Debugging of JavaScript code is supported in the Firefox and Google Chrome browsers by means of browser-specific JetBrains extensions. No special steps are required from your side to install or enable these extensions. WebStorm does it for when you initiate a debugging session for the first time.

During a debugging session, WebStorm considers any injected JavaScript code in a Web page opened in the browser as subject for debugging. This means that you cannot use the same instance of a browser for browsing and for debugging simultaneously. For Google Chrome you can solve this problem by configuring WebStorm to use a separate Chrome user profile for debugging.

In this section:

Configuring the Settings for Debugging JavaScript Code

  1. Open the Settings / Preferences Dialog by choosing File | Settings for Windows and Linux or WebStorm | Preferences for OS X. Expand the Build, Execution, Deployment node, and then click Data Views under Debugger.
  2. On the Data Views page that opens, specify the following:
    • Use the Built-in server port spin-box to specify the number of the port where the built-in web server runs. The port number should be set to 1024 or higher. By default this port is set to the default WebStorm port through which WebStorm accepts connections from services (63342). During a debugging session, the Chrome extension will listen to this port. If for some reason the default WebStorm port is already busy, WebStorm finds the closest available port and starts on it. This results in a conflict: WebStorm is running on a "new" port while the Chrome extension still listens to the port of a previously started product and fails to establish connection with WebStorm. The conflict reveals when you initiate a debugging session from WebStorm: the extension fails to connect through the default port, WebStorm waits for connection from the extension and displays the following message with the port number where it is actually running:

      To fix the problem, specify the actual port in the Chrome extension options, see Using JetBrains Chrome Extension.

    • In the Value tooltip delay (ms) field , specify the time period between pointing at an object and displaying the object's value in a tooltip.
    • Whether to display DOM properties in a tab or not.
    • Whether to display function values in a tab or not. If you want the function values to be shown only for user-defined functions, select the Show only user-defined functions. (Otherwise, the function values will be shown for all function.)
    • Whether you want object node properties to be shown. If so, specify the properties. Use add and delete to manage the list of properties.
    • Whether you want the debugger to skip certain scripts. If so, specify URLs for the corresponding scripts. Use add and delete to manage the list of script URLs.

See Also

Last modified: 11 July 2016