Provide a diagnostic tool

[roblourens]

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.

[jasonwilliams]

Yes please, this would make debugging these issues much easier

[connor4312]

Could even pop open the browser and/or write an HTML file with details. We have a lot of data and being able to display it in a richer form than the debug console may make life easier. The analyzer could be built into it as well. That alone would make my debug loop a little faster.

[roblourens]

Sort of related, I have imagined a workflow where you can click a source that looks like webpack://mycode.ts and pick the file on disk that it corresponds to, and we would generate the launch config parameters to produce that correct mapping.

[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)