Map paths for console.error(...)

[s4m0r4m4]

Original discussion in the 'vscode-chrome-debug-core' repo here: microsoft/vscode-chrome-debug-core#553

Long story short, I would like to request a feature in which console.error() messages are also processed to map paths back to source files. This would be helpful for angular developers where the main typescript file that bootstraps the app is setup to catch any errors and use console.erorr() to display them in the console. Please let me know if you need more info!

[connor4312]

Good idea, should be fairly easy

[connor4312]

This might slip to June. The stacks of logged errors isn't easy to pluck out--we need to actually do some string parsing. This introduces some complexity, and at the moment the console message handling we do is very simple and imperative. I'd like to clean up and extract some of this logic rather than tacking it onto what we have today.

[s4m0r4m4]

Thanks for the update! I appreciate it.

[connor4312]

[roblourens]

I think this isn't working for me. Just added console.error(new Error('fail')) to some TS.

vscode-debugadapter-4.json.gz

[roblourens]

[connor4312]

It looks like the first line of the stack isn't in parens, so our regex doesn't match it.

It should match the 3rd line, but that looks like it's in a TS header that won't have a source map location.

[bpasero]

Unclear how to verify.

[weinand]

*.js files are mapped back to *.ts (if possible):