[Feature]: Provide error stack-traces evaluating source-maps

[MiladSadinam]

🚀 Feature Request

Playwright documentation (https://playwright.dev/docs/api/class-consolemessage) recommends the following code to retrieve console errors:

page.on('console', msg => {
  if (msg.type() === 'error')
    console.log(`Error text: "${msg.text()}"`);
})

We use this to create a simple trace for failed tests on our CI system. Our CI system uses minefield builds but with generated source maps. Still, msg.text() ignores any source maps, making the stack trace useless. It would be very helpful if Playwright provided stack traces that already took source maps into account.

Example

No response

Motivation

Provide meaningful stack traces in CI systems that use minified builds because of performance considerations.

[yury-s]

This is something you need to address in the web app/its build configuration or implement on top of Playwright. Playwright doesn't do anything specific for the messages in the web page in browser.

[vctqs1anz]

Hi @yury-s I know this issue has been closed for a while, but I’m also looking for something similar.

Even though the application provides source maps, I can only see the mapped error traces in the Playwright Chrome while running tests locally.

However, this information isn’t stored in Playwright traces, which makes it quite difficult for us to trace errors when tests are running in CI.