Provide a diagnostic tool

The v1 adapter has the .scripts command which dumps info about which scripts are loaded, the sourcemap info, and how the paths are finally resolved after applying overrides. It would be useful to have the same in this adapter. Would be awesome to have this in GUI form, a custom treeview, or opening an editor with a nicely formatted markdown grid, or something more user friendly than what v1 does.

[sippeangelo]

The command seems to have been renamed to Diagnose Breakpoint Problems and it’s only available while a debug session is active!

[connor4312]

Added a new command Create Diagnostic Information which generates a nice .html report. Example: https://memes.peet.io/img/js-debug-diagnostics2.html

• shows current sources and shows you sourcemap children/parents
• has a ‘breakpoint fixer’ that checks for a few common cases
  • a breakpoint set in a file that was missing. Will show if there are any files of the same name in the runtime.
    • For .ts/x files it suggests adding sourceMap: true to the tsconfig.json if no files are found
    • For web launches it suggests changing the webRoot
    • If it sees the user specific outFiles, it suggests removing the glob (since we default to the workspace)
  • Breakpoints where they match a file, but are unbound by the runtime (almost always outdated sources or bad locations)