Skip to content
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

Debugging ClearScript with Visual Studio Code #573

Open
flat-eric147 opened this issue May 2, 2024 · 1 comment
Open

Debugging ClearScript with Visual Studio Code #573

flat-eric147 opened this issue May 2, 2024 · 1 comment
Assignees
Labels

Comments

@flat-eric147
Copy link

Hi there,
I am currently trying to figure out who to debug and ideally modify my ClearScript code through Visual Studio Code. I am surprised to find that it does not work as good as with chrome inspector. It seems the extension on which ClearScript was tested and documented is now obsolete.
debugextensionobsolete
Instead the "Javascript Debugger" seems to be the new default. The launcher settings "protocol":"inspector" don't seem to work anymore on this.
javsascripdebug

While using this debugger, I am unable to modify code when in break mode, and thus it can't be pushed back to ClearScript. I tried also with a local module which I imported, even when I modify that, changes on that external module are not applied to the running script.

I suspect ClearScrip does not support this new/different debug commands coming from vscode, but I'm not an expert on this unfortunately.

Any input or ideas on this, perhaps I'm just doing it wrong :) Thank you!

@ClearScriptLib
Copy link
Collaborator

Hi @flat-eric147,

I suspect ClearScrip does not support this new/different debug commands coming from vscode

ClearScript's role in V8 debugging is limited to providing a communication channel between V8 and the debugger. It isn't involved in the implementation of the debugging protocol itself.

It's possible that newer V8 versions provide debugging hooks that ClearScript doesn't yet support, and we'll take a closer look at that, but differences in debugging functionality are most likely due to differences in the debuggers.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants