-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CDP Proxy: Allows Other Extensions to Reuse CDP Connection #964
Conversation
Would it make sense to expose the underlying error here https://github.com/microsoft/vscode-js-debug/blob/main/src/cdp/connection.ts#L271, instead of masking it with |
Yea, the error should be exposed. I'll play around with it. I would prefer to throw/reject with errors, but we depend on omitting the error in so many places throughout js-debug that changing this would be quite risky. |
@swissmanu can you give me permission to push to your fork please? 🙂 |
In the meantime I've pushed my changes onto a branch in 0c6bd3f. As referenced in the commit, I moved the protocol to CDP with a js-debug extension. This simplifies things but it might still be worth publishing a typings package for the js-debug namespace -- right now this is just the single Also, now that it's 'just CDP', maybe I should finally look at making js-debug's CDP transports and mechanisms their own package... |
I ticked the "Allow edits by maintainers" checkbox on this pull request only. Permissions to the fork should be work by now. Sorry for the delay.
I like like your removal of the additonal protocol layer. Makes things straight forward. |
🚀 Thank you for your work on this! |
Extends
js-debug
to expose its internal CDP connection to other extensions.This pull request resolves #893.
Overview
requestCDPProxy
returns websocket connection details to connect to the CDP proxy.requestCDPProxy
is called the first time, the proxy is created