-
Notifications
You must be signed in to change notification settings - Fork 119
Breakpoints never hit for typescript #255
Comments
I assume this is node?
Well, there's your problem :) It is required for this scenario. |
You are right : this is node. |
But we can't resolve from source -> generated script without knowing where the generated script is in the first place. |
You are right. So, the only way would be to pause on every script entry in |
We are implementing something like this in #241 for chrome-debug, but I think |
In debug mode, I don't really care about runtime perf, so I need your expertise because I need it to work for node (DOMDebugger breakonload is only for browser I think).
I can manually resume in vscode ide, but I can't find a way to resume from vscode-chrome-debug-core programmatically. Thank you in advance to help me a little more. |
That's not guaranteed to work, because the script is still running at the same time that code is trying to set a breakpoint. The PR I linked implements two strategies, one using the DOMDebugger api, another that optimistically sets breakpoints by guessing likely file names. But... just set |
My goal is always the same : to get inline sourcemaps from
In my previous post, the breakpoint is set at the beginning of Helloworld.ts which is the next script to run: only entry.js is running at that time. So, if I can resume using the ide toolbar, why not programmatically. Is there an onPaused event from vscode ide somewhere to be able to call resume programmatically ? I think it just need to wait until all the core workflow is done to resume. |
Hello,
Here is the steps to reproduce:
The breakpoints are never hit because sourcemap file is processing too late.
I use es6 in tsconfig and I don't add outFiles to launch config.
The text was updated successfully, but these errors were encountered: