Debugging

• Debugging
  • Overview
  • General debugging steps
• Breakpoints
• Using Breakpoints
• Configuring Debugger Options
• Starting the Debugger Session
• Stepping Through the Program
• Pausing and Resuming the Debugger Session
• Examining Suspended Program
• Finding the Current Execution Point
• Monitoring the Debug Information
• Live Editing of HTML, CSS, and JavaScript
• Viewing Actual HTML DOM
• Tracing with Spy-js
• Inline Debugging

Overview

This section describes the procedures that are common for various types of applications.

For details on debugging applications in the supported frameworks, refer to Languages and Frameworks.

WebStorm provides a full range of facilities for debugging your source code:

• Breakpoints in HTML, and JavaScript.
• Customizable breakpoint properties: conditions, pass count, etc.
• Frames, variables, and watches views in the debugger UI.
• Runtime evaluation of expressions.

If you want to see a list of all currently debugging applications, select Run | Show Running List from the main menu. Refer to the section Viewing Running Processes for details.

General debugging steps

1. Configure the debugger options.
2. To debug CoffeeScript, TypeScript, and Dart code, you need source maps generated in addition to the JavaScript code.

   Source maps set the correspondence between lines in your original code and in the generated JavaScript code, otherwise your breakpoints will not be recognised and processed correctly.

   JavaScript and source maps are generated by compiling the original code either manually using the File Watcher of the type CoffeeScript, or by the built-in compiler (for TypeScript), or through integration with the Pub Serve tool (for Dart). After that, you can debug the output JavaScript code. See Compiling CoffeeScript to JavaScript, Compiling TypeScript to JavaScript, and Using Integration with the Pub Tool for details.

3. Define a run/debug configuration for the application to be debugged.
4. Create breakpoints in the source code.
5. Launch a debugging session.
6. Pause or resume the debugging session as required.
7. During the debugger session, step through the breakpoints, evaluate expressions, change values on-the-fly , examine suspended program, and set watches .

After you've started a debug session, the icon that marks the Debug tool window toggles to to indicate that the debug process is active.