#Webstorm node debugger manual#
#Webstorm node debugger code#

The Run tool window or the Terminal shows the URL at which your application is running.

Start the application in the development mode, for example, using an npm script. Just hold Control+Shift and click the URL at which the application is running. If your application is running in the development mode on localhost, you can start debugging it from the built-in Terminal ( Alt+F12), from the Run tool window, or from the Debug tool window. Debug an application that is running on the localhost in the development mode Clicking the Reload in Browser button ( ) reloads the calculator.html page so all the previous script output is cleared and the debugger returns to line 1 in Calculator.js.

The starting home.html page has a Submit button on pressing which the calculator.html page opens with the results of the Calculator.js script execution.ĭuring a debugging session, clicking the Rerun button ( ) would reload the home.html page with the Submit button. The example below shows a simple application that consists of two HTML pages and a JavaScript script. This works the same way as the Reload Page functionality ( Control+R) in Chrome. Reload the current page in browserīesides restarting your application by clicking the Rerun button ( ) in the Debug tool window, you can also click the Reload in Browser button ( ) to reload the page where you have currently navigated. To restart the new run/debug configuration, click ( ) on the toolbar or select Run | Debug from the main menu. WebStorm creates a run/debug configuration automatically, and a debugging session starts. To start debugging this application using the built-in server, open index.html in the editor and choose Debug 'index.html' from the context menu. Let's suppose that you have a simple application that consists of an index.html file and an index.js file, where index.html references index.js. To open a new Chrome instance with your familiar look-and-feel, configure Chrome in WebStorm to start with your user data, see Starting a debugging session with your default Chrome user data for details.

#Webstorm node debugger code#

In the Debug tool window, proceed as usual: step through the program, stop and resume the program execution, examine it when suspended, view actual HTML DOM, run JavaScript code snippets in the Console, and so on.īy default, a debugging session starts in a new window with a custom Chrome user data. To save the automatically generated configuration for further re-use, choose Save from the context menu after the debugging session is over. The file opens in the browser, and the Debug tool window appears. WebStorm generates a debug configuration and starts a debugging session through it. Open the HTML file that references the JavaScript to debug or select the HTML file in the Project tool window.įrom the context menu of the editor or the selection, choose Debug. Set the breakpoints in the JavaScript code, as required. All the project files are served on the built-in server with the root URL with respect to the project structure.

#Webstorm node debugger manual#

This server is always running and does not require any manual configuration. WebStorm has a built-in web server that can be used to preview and debug your application. For more details about the live editing functionality, see Live Edit in HTML, CSS, and JavaScript.ĭebug an application that is running on the built-in server To have the changes you make to your HTML, CSS, or JavaScript code immediately shown in the browser without reloading the page, activate the Live Edit functionality. For more details about plugins, see Managing plugins.Ĭonfigure the built-in debugger as described in Configuring JavaScript debugger. In the search field, type JavaScript Debugger. Press Control+Alt+S to open the IDE settings and then select Plugins. Make sure the JavaScript Debugger bundled plugin is enabled in the settings.