You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With #902 being resolved, I happily manage to use vscode-js-debug for JS files in Eclipse IDE using pwa-node. However, despite having attempted a bunch of things according to various docs or examples I've seen, I didn't manage yet to debug even the simplest typescript example:
I suspect there are some params I'm missing in the request, but I can't find a way to determine which one(s) are necessary for proper execution.
Does anyone have a clue? The best format would be an automated test case to show what's need for TS debugging.
The text was updated successfully, but these errors were encountered:
OK, thanks. I could verify it works.
Do you think the debug adapter could take care of that resolution from .ts to .js? If not, I'll just close the issue, if yes, I will rephrase the title to make it read more like a feature request.
Not sure entirely what's going wrong without debugging it some more; I can see if I can reproduce it with a pure DAP server in next debt week. PR's also welcome if you're feeling intrepid.
With #902 being resolved, I happily manage to use vscode-js-debug for JS files in Eclipse IDE using
pwa-node
. However, despite having attempted a bunch of things according to various docs or examples I've seen, I didn't manage yet to debug even the simplest typescript example:with a tsconfig.json
and .js and .js.map files in the .build/ folder.
The issue I see is that the DAP seems to always interpret my file as a .js file and complains it cannot be parsed.
and here is the launch request sent by the client to the Debug Adapter:
I suspect there are some params I'm missing in the request, but I can't find a way to determine which one(s) are necessary for proper execution.
Does anyone have a clue? The best format would be an automated test case to show what's need for TS debugging.
The text was updated successfully, but these errors were encountered: