How it works...
WebStorm's debugger connects to the same Node inspector process that Chrome's developer toolkit does. It leverages this process to communicate with the running Node.js process and send messages, including application state and debugging instructions back and forth with Node and V8. The big enhancement here from Chrome is that code is being debugged directly beside the source code. So, making changes to code directly is very easy to do while inspecting values. However, this doesn't change how Node as a process runs and makes edits to source code, and debugging will not be swapped inside V8. The only way to change source code in a running Node.js debug session is to restart the process.
The main debugging interactions in WebStorm ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access