-
Notifications
You must be signed in to change notification settings - Fork 72
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
Use vscode-js-debug in place of deprecated node-debug2 #1174
Use vscode-js-debug in place of deprecated node-debug2 #1174
Conversation
See microsoft/vscode-js-debug#926 (comment) about getting dapDebugAdapter conveniently. |
d398677
to
c09b332
Compare
IP review submitted: https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/10778 |
c09b332
to
dcc6209
Compare
Moving back to draft as there are still 2 important limitations:
|
In theory this also replace deprecated chrome debug adapter (pwa-chrome) and supports edge (pwa-msedge, windows only) |
Both issues listed are fixed in LSP4E DAP support, but there is another issue that now |
0cae91b
to
f4f73c3
Compare
At the moment, I didn't manage to get a TypeScript program being debugged... |
Submitted question to microsoft/vscode-js-debug#1838 |
f4f73c3
to
de7ddb9
Compare
This also restore ability to debug running Node processes (eg start with --inspect). Requires usage of latest LSP4E support for DAP. Fixes eclipse-wildwebdeveloper#555
de7ddb9
to
91482eb
Compare
b6e8837
into
eclipse-wildwebdeveloper:master
@mickaelistria I installed the latest snapshot and I'm not able to debug js files with this new debug. I created a simple js file, right clicked on the file and selected
The console prints the message:
How do I debug? |
Can you please open a new issue about this and share the content of workspace/.metadata/.log ? |
This was drafted while working on
startDebugging
support for LSP4E.Before we can merge in Wild Web Developer, this requires the following issues to be fixed