Description
NOTE: Background reading and resources at the end of this post.
CDP groups functionality into Domains containing Methods, Events, and Types. The domains and members supported by a given runtime/debug target can be specified in a protocol.json
file, ideally retrievable dynamically by the debugger at a /json/protocol
endpoint on the debugee. Examples and discussion:
- Blink
- Edge (see Microsoft/edge-diagnostics-adapter#24)
- cyrus-and/chrome-remote-interface#10, cyrus-and/chrome-remote-interface#24
V8's currently-supported Domains are listed here.
For Node to fully support CDP we must implement and specify which Domains and other members Node supports, likely in a protocol.json
file, and likely starting from those supported by V8 and the inspector agent. We could call this the Node "profile" for CDP.
This was discussed in #49's meeting.
- This issue is to track progress on creating such a profile for Node.
Background and Resources
Please suggest more in the thread and I'll add them.
- CDP == Chrome Debugging Protocol
- Google's help page on CDP
- @auchenberg's list of related specs