Debugger/Chrome DevTools umbrella issue

[bartlomieju]

• Can't debug multiple test files in VS Code using deno test deno#13152
• Not possible to debug worker deno#13572
• When using --inspect wait a little bit for inspector connection at program start deno#13664
• Debugging broken deno#13908
• [Debug Mode] Debugger doesn't terminate when code finishes or error **IF** a NPM package is inside deno.lock deno#16662
• Busy-loop code makes it impossible to attach inspector deno#16725
• --inspect-brk doesn't stop execution when running global npm commands deno#16757

[khrj]

Possibly relevant: denoland/deno#16757

[jespertheend]

I'm running into an issue where sometimes the debugger pauses correctly (because it stops logging things to the console), but VSCode doesn't display the paused breakpoint.
To work around it, I can detach the VSCode debugger and reattach it. For some reason the debugger will stay paused even with no debugger attached. Once reconnected, VSCode displays the breakpoint at which the debugger is paused.

edit: I think this is basically denoland/deno#13152 because I'm debugging multiple test files.