Therefore, when Chrome Debugging Protocol is used, WebStorm always starts a debugging session with in a new window with a custom user data. However, if Chrome is already started, a debugging port can't be opened for any new or existing Chrome instance that has the same user data. That happens because WebStorm uses Chrome Debugging Protocol and runs Chrome with the -remote-debugging-port option. As a result, the window looks unusual, for example, your bookmarks, the browser history, and the extensions are missing, which altogether breaks your development experience. You may notice that your debugging session starts in a new window with a custom Chrome user data instead of your default one.
Starting a debugging session with your default Chrome user data To expand the suppression list, select Do not step into scripts checkbox and add the URL addresses to skip using and. Stepping page, specify the scripts to be skipped by the debugger.īy default, the debugger does not step only into library scripts. Data Views page under the Debugger node, configure advanced debugger options: enable or disable Inline Debugging, specify when you want to see tooltips with object values and expressions evaluation results, and so on. Suppress calls to the files on the built-in server from other computers or from outside WebStorm by clearing the Can accept external connections or Allow unsigned requests checkbox respectively.Ĭhoose the way to remove breakpoints, the default setting is Click. You can set the port number to any other value starting from 1024. By default this port is set to the default WebStorm port 63342 through which WebStorm accepts connections from services.
In the Built-in server area, specify the port where the built-in web server runs. Press Ctrl+Alt+S to open the IDE settings and select Build, Execution, Deployment | Debugger. Make sure the JavaScript Debugger bundled plugin is enabled on the Settings/Preferences | Plugins page, tab Installed. To ensure successful debugging, it is enough to specify the built-in web server port and accept the default settings that WebStorm suggests for other debugger options. The built-in debugger starts automatically when you launch a debugging session. WebStorm provides a built-in debugger for your client-side JavaScript code.
#Google chrome script debugger code
Debugging of JavaScript code is only supported in Google Chrome and in other Chromium-based browsers.
0 kommentar(er)
