VSCode Extension Debug: Breakpoints in Sourcemaps not set when --profile-temp is used. about vscode-js-debug HOT 8 CLOSED

Yea, it works with sourcemaps as well for me (using the helloworld-sample).

from vscode-js-debug.

Can you use "trace": { "logFile": "${workspaceFolder}/log.txt" } so that logs are saved as a plain .txt file, and share those here? That may provide a hint.

from vscode-js-debug.

I'm not able to repro this.

Unfortunately it looks like the log files didn't get recorded correctly. Can you use "trace": { "logFile": "${workspaceFolder}/log.txt" } so that logs are saved as a plain .txt file, and share those here?

from vscode-js-debug.

@connor4312 thanks for taking a look, I'll give it another shot and produce a fresh repo repository. Are you sure you're using sourcemaps here? I don't see a sourcemap file in your repo screenshot

from vscode-js-debug.

So I'm still getting it with a fresh "host" profile and debug configs for profile and profile-temp using helloworld-sample. Wondering if it's something about my computer specifically (Windows), let me try it in a codespace.

from vscode-js-debug.

OK so I can't reproduce in a fresh codespaces with helloworld-sample, but one thing interesting I noticed is that the breakpoint doesn't bind until the extension activates. Is this normal or expected? I could see this being super confusing and this might be where I got hung up in I didn't see the breakpoint bind but didn't actually try to run the specific code.

Also it's not super clear from this video but I've tried also waiting quite a while for the breakpoint to bind, it stays gray all the way up to running the command and then suddenly hits.

Video:

Here's the log:
log.zip

from vscode-js-debug.

That being said, I'm not reproducing this in sample-helloworld so I'll see if I can reproduce where I was seeing it and produce a simpler repro. Thanks! I'll open breakpoint as a separate issue.

from vscode-js-debug.

One thing interesting I noticed is that the breakpoint doesn't bind until the extension activates. Is this normal or expected?

Yea, until the runtime acknowledges the breakpoint, it's shown as unbound.

from vscode-js-debug.