Deno with the --inspect-wait arg doesn't expose /json/protocol - should it?
I'm testing out connecting to a Deno process via the v8 inspector protocol: https://deno.land/manual@v1.36.2/basics/debugging_your_code and discovering that though it seems to work with Chrome and certain other tools, trying it with chrome-remote-interface https://github.com/cyrus-and/chrome-remote-interface says that it doesn't expose an endpoint at
/json/protocol. I've tried Node, and it does expose an endpoint there and list its capabilities with JSON. Is this not part of the v8 protocol but something else? Maybe this is something Deno hasn't implemented?Deno
Debugging Your Code | Manual | Deno
Deno supports the V8 Inspector Protocol used by
Chrome, Edge and Node.js. This makes it possible to debug Deno programs using
Chrome DevTools or other clients that su
GitHub
GitHub - cyrus-and/chrome-remote-interface: Chrome Debugging Protoc...
Chrome Debugging Protocol interface for Node.js. Contribute to cyrus-and/chrome-remote-interface development by creating an account on GitHub.
3 Replies
Providing a hardcoded protocol.json does make chrome-remote-interface work, though it's hard to tell which methods are and aren't supported by Deno without protocol.json
Have you tried swapping
--inspect-wait for --inspect-brk? Though that would be more of a test than a solution to the problem@tmcw we don't expose that endpoint. Seems like an easy fix, can you open an issue?