Add support of node.js via new v8_inspector in Node core

[auchenberg]

As of nodejs/node#6792, Node will support the Chrome Debugging Protocol in it's core via the v8_inspector project contributed by Google.

From reports by @nojvek, the current debugger doesn't work with the Node PR. We should make sure our core debugger works with this potential future version of Node.

[nojvek]

I didn't dig deeper but it seems we expect an inspectable page for vscode.
Will debug more and report back on another thread.

Ideally now that the protocol is getting support from different run times,
I would really love to see an effort where this becomes a JavaScript
debugging protocol with extensions that is managed by a working group
similar to w3c.

Happy Memorial Day.

On Monday, May 30, 2016, Kenneth Auchenberg notifications@github.com
wrote:

As of nodejs/node#6792 nodejs/node#6792, Node
will support the Chrome Debugging Protocol in it's core via the
v8_inspector project contributed by Google.

From reports
nodejs/node#6792 (comment) by
@nojvek https://github.com/nojvek, the current debugger doesn't work
with the Node PR. We should make sure our core debugger works with this
potential future version of Node.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#17, or mute
the thread
https://github.com/notifications/unsubscribe/AA-JVH2Xqod-rwFEptZh1hpQGdY_6SEeks5qGtKMgaJpZM4IpvgS
.

[auchenberg]

This feature is current blocked by an invalid webSocketDebuggerUrl returned from the HTTP /json endpoint in Node. Issue been opened, nodejs/node#7227.

In addition we need to modify the target filering logic that's currently discarding node targets, which has the type : node

[roblourens]

See https://github.com/microsoft/vscode-node-cdp-debug

[niieani]

@roblourens the link you provided is (now) 404.

[roblourens]

The repo is private at the moment - we'll open it up sometime soon.