-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Support debugging VS Code extensions via the debug view #4016
Comments
@akosyakov there is a command called "Hosted Plugin: Debug Instance" available from the command palette. Does that fulfil your need? |
It is about the convenient dev flow for existing VS Code extension developers, that they can specify custom debug configuration and run it with one hit of |
One can setup node debug configuration for time being, it is quite straightforward, see #3251 (comment) |
Hi @akosyakov, |
Nope, it is free to grab. VS Code exposes a command for Node.js debug extension to start another instance of VS Code. We should implement such command and start another instance of Theia plus translate arguments. |
@amiramw please assign @danarad05 to this issue. |
Hi @akosyakov @tsmaeder @amiramw @DoroNahari, I need some assistance here. As far as I understand task I need to add another launch configuration to existing default launch configurations - here: After debugging, I found that list of default configurations are coming from vscode builtin plugins: Questions:
Thanks -Dan |
@danarad05 in vcsode there is a launch configuration type called Maybe try to look into this repo. vscode-node-debug2 is loaded in theia: https://github.com/eclipse-theia/theia/blob/master/package.json#L122 |
@amiramw Thanks, I'll check it but there is still same issue as in my question #2 above as vscode-node-debug2 plugin is also a microsoft vscode repo - https://github.com/microsoft/vscode-node-debug2. |
You don't need to add any new configurations. They are already contributed by node 2 vscode built-in extension. You only need to implement a command which this extension is calling to start another instance of VS Code. |
@akosyakov by command you mean theia cli option? |
There should be a debug configuration provider for
extensionHost
debug type. It allows a user to create a proper node debug configuration and does not require any extra UI.The text was updated successfully, but these errors were encountered: