-
Notifications
You must be signed in to change notification settings - Fork 2
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 extension with VSCode #29
Comments
@genius257 When I use the |
This is what I see in the terminal --
and it never proceeds beyond this point. If I press Ctrl+C, it asks if I want to exit the batch file. I answered No, and then it proceeded to load the separate instance of VSCode with the extension running. Could this be caused by an outdated library, Node, etc? |
Seems like |
Make some headway by installing this extension and then adding the following to tasks.json -- {
"type": "npm",
"script": "build",
"group": "build",
"problemMatcher": ["$ts-webpack", "$tslint-webpack"]
},
{
"type": "npm",
"script": "watch",
"group": "build",
"isBackground": true,
"problemMatcher": ["$ts-webpack-watch", "$tslint-webpack-watch"]
} Now the client launches successfully, but I'm not sure if the server attach is working (all breakpoints still appear as unbound). |
I'll be honest, i haven't tried the |
A small update: missing configuration from the .vscode/tasks.json seemed to be the issue for the npm watch task seemingly being stuck. I'm still not at testing with breakpoints yet, but I will let you know when i progress more! 😄 |
So based on this i can see the The only way I've found for getting working breakpoints on the server code so far, is to
It is very disappointing and surprising to me that the combination of poor example quality they provide, combined with this problematic debuggability. |
This issue appears related -- |
Very nice! 😄 |
So the relevant vscode issue was finally "resolved". My issue is that I'm using a development container for my node runtime and debugging extension from a devcontainer seems to be broken and i cannot find much information about it so far. I have not abandoned hope, and will revisit this issue at a later date (repeatedly if i haft to), but for now i will focus on getting the extension usable and stable. Sorry for the long wait for the disappointing update 😞 |
Are you running the code using the
"Client + Server"
option from the drop-down list in the debug tab?Originally posted by @genius257 in #27 (comment)
The text was updated successfully, but these errors were encountered: