Connor Peet

This should not happen in Node (+ Node doesn't support the sourcemap breakpoint used in browsers). Can you capture a trace log using these instructions? >If you're able to, add...

@KrakenZ apps shouldn't take that long! Please collect a trace log using these instructions: > If you're able to, add `"trace": true` to your `launch.json` and reproduce the issue. The...

@KrakenZ thanks for the log! You're running into https://github.com/microsoft/vscode-js-debug/issues/598 which is fixed in the latest [nightly build](https://github.com/microsoft/vscode-js-debug#nightly-extension).

Good to hear! I'll keep this issue open to attempt to address the cosmetic flickering issue. It will still happen even with that fix (just a couple times, though, instead...

We will need a fix in Chrome for this. Tracking this here: https://bugs.chromium.org/p/chromium/issues/detail?id=1131204

You may be able to add `"perScriptSourcemaps": "yes"` to your launch.json to use an improved behavior that might work better, looks like the automatic detection did not trigger on your...

Thanks for the logs. It looks like it's actually working correctly, but in your code is still hitting a lot -- normally we request the runtime to pause before any...

Sure, a PR is welcome. Note this is actually implemented in https://github.com/microsoft/vscode/tree/main/extensions/npm

I'm not a big fan of this. Maybe a more generalized solution would be a button in the title of the Variables view that hides properties with `presentationHint.visiblity === 'internal'`....

>If you're able to, add `"trace": true` to your `launch.json` and reproduce the issue. The location of the log file on your disk will be written to the Debug Console....