Breakpoints in JS client (Chrome) not working in 2019.2 from external server
Hi,
I upgraded to WS 2019.2 yesterday and my client-side javascript breakpoints stopped working! It was working in 2019.1. I am using an external web server start was started in debug mode (node version 4.x) and not the built-in webserver. I can see the console output coming through, but the breakpoints never hit. Any ideas?
Thanks,
Joel
WebStorm 2019.2
Build #WS-192.5728.87, built on July 22, 2019
Runtime version: 1.8.0_211-b12 amd64
VM: Java HotSpot(TM) 64-Bit Server VM by Oracle Corporation
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1518M
Cores: 4
Registry: ide.editor.tabs.open.at.the.end=true, debugger.mayBringFrameToFrontOnBreakpoint=false, js.debugger.webconsole=false
Non-Bundled Plugins: com.khmelyuk.multirun
Please sign in to leave a comment.
Got it working, had to set my Remote URL in the Run/Debug Configuration (didn't have to do this before, so not sure why that changed). Thanks!
Joel, I am having this same issue. What do you mean you had to set the Remote URL? When I click 'Debug' it will open a new window with the given url and like you stated I see the console output, but my breakpoints are not being hit, the only way I can get them to activate is by actually placing a break point in the source file in Chrome.
Joel, I had the same aha moment!! You are correct this is all I had to do as well! Thanks for the solution!
Please see https://www.jetbrains.com/help/webstorm/2019.2/debugging-javascript-on-an-external-server-with-mappings.html#ws_js_debug_on_remote_server_mappings
For example, if your web server serves files from the public folder, you need specifying URL mappings for this folder, like:
>didn't have to do this before, so not sure why that changed
please follow https://youtrack.jetbrains.com/issue/WEB-40437 for updates