Re: [v8-users] Debugger acting as a client connecting to the server

Hey Demurgos, Having been one of the folks who inflicted spawn-wrap on the world, I couldn't be more excited to retire it... I've been advocating that we better expose v8 code coverage in Node.js itself; in a perfect world you'd do something like this: `node --coverage foo.js` and along with

Re: [v8-users] Debugger acting as a client connecting to the server

+yang who can say more about node. We (Ben, Yang & myself) recently discussed the possibility of adding coverage support to node itself. See here for a (very rough and early stage) doc with some

[v8-users] Debugger acting as a client connecting to the server

Hi, I work on Node.js code coverage tools using V8's profiler (c8). There are currently 2 methods to use the V8 debug protocol from Node. 1. You can spawn a process with the `--inspect` or `--inspect-brk` flag. This starts V8 in "server mode" and remote clients can connect to it and interact