Updating server app disconnects debugger

Each time I choose to update my server app, the debugger is disconnected.  This is new behavior.  Not sure if it happened after my recent Webstorm upgrade but it seems likely.

How can I do a server update and keep the debugger connected?

Thanks, Mike

8 comments

Is it about Node.js debugging? Do you debug locally (via Node.js run configuration + local interpreter), or remotely (with Attach to Node.js/Chrome run configuration, or with remote interpreter)? What webStorm version do you use?

0

HI I'm using Webstorm 2017.3.4 and this is using Node.js with Chrome debugging.  I used to be able to update application and continue to debug the server, but no longer.  Now I have to restart the server app every time I make a change which is an impossible way to work.

0

Sorry I'm confused if this is same as my issue.  Are you suggesting that there is a bug in Webstorm and I should wait for a fix?  

 

Regardless, in that problem report they talk about reconnecting the debugger.  I would love to be able to do that but I hve no idea how.  I'm stuck so far with having to completely shutdown my app and restart it.  Can you please explain how I can connect a debugger to my running node app?

0

Sorry again but my problem is not with the Chrome local debugger. That is working fine. I can refresh the browser and it still works fine. The problem is with the server app. If I update that code and choose to update application in Webstorm, the server side debugger has quit and none of my breakpoints are honored.

0

>Sorry again but my problem is not with the Chrome local debugger. 

 

and https://youtrack.jetbrains.com/issue/WEB-25672 is not about Chrome local debugger, it's about connecting to remote Node.js app via Chrome debugging protocol (Attach to Node.js/Chrome run configuration)

0

Is this scheduled to be fixed?  Also, there was mention of live edit.  Would this help my problem?

0

If you are using nodemon or another tool that restarts your server automatically on making a change, you can try using live edit _instead_ of this tool - it normally hotswaps changes to server or auto-restarts it, keeping the debugger connected. However, Live edit doesn't work reliably with Node.js 8 + (https://youtrack.jetbrains.com/issue/WEB-29792)

0

Please sign in to leave a comment.