The list_console_messages tool should include the source location where a message originated from

[szuend]

Is your feature request related to a problem? Please describe.

At the moment, the user has to use get_console_message and look at the stack.

Describe the solution you'd like

It would be neat if console messages/uncaught errors include the source-mapped location of where they come from. Its the same as the top-most frame in the stack trace.

Describe alternatives you've considered

See above.

Additional context

No response

[kopalg20]

I’d like to take this on if it’s still available.
@szuend and @OrKoN

It looks like the correct place to implement this would be in ConsoleFormatter, by exposing the top-most non-ignored frame (already source-mapped via uiLocation) in toJSON() and toJSONDetailed(). That way, list_console_messages can include the location without changing tool logic or response handling.

Let me know if this approach aligns with the intended design and I can start working on it.

[OrKoN]

So the process of fetching source maps is async (list_console_messages does not fetch those right now) and it is potentially performance intensive. We should implement in a way that does not block the list_console_messages and test it on a test page with large source map and many error message to ensure the performance is acceptable. Happy to review a PR.

[kopalg20]

Thank you for mentioning this @OrKoN.
I have creater a PR for this let me know for any improvements on the same:
#960