feat: include source-mapped stack trace for uncaught errors#876
Merged
Conversation
szuend
commented
Feb 3, 2026
OrKoN
approved these changes
Feb 3, 2026
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 4, 2026
🤖 I have created a release *beep* *boop* --- ## [0.16.0](chrome-devtools-mcp-v0.15.1...chrome-devtools-mcp-v0.16.0) (2026-02-04) ### 🎉 Features * include source-mapped stack trace for uncaught errors ([#876](#876)) ([ecef712](ecef712)) ### 🛠️ Fixes * accidental extra typing in the fill tool ([#886](#886)) ([3d6e59d](3d6e59d)) * update evaluateScript description formatting ([#880](#880)) ([24db9dd](24db9dd)) * use 1-based line/column and fix wasm offsets in stack frames ([#884](#884)) ([7e1ec81](7e1ec81)) ### 📄 Documentation * mention source-mapped stack traces in 'Key features' ([#883](#883)) ([579d18a](579d18a)) * remove outdated --channel=beta note ([#882](#882)) ([acdb5c9](acdb5c9)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
wolfib
pushed a commit
to wolfib/chrome-devtools-mcp
that referenced
this pull request
Mar 10, 2026
…vTools#876) Note that we replace the existing "pageerror" handler with our new `UncaughtError` handler. The latter has a structured stack trace attached which we can source map via DevTools. This regresses the current functionality slightly, as we lose "pageerror"s for workers and oopif.
wolfib
pushed a commit
to wolfib/chrome-devtools-mcp
that referenced
this pull request
Mar 10, 2026
🤖 I have created a release *beep* *boop* --- ## [0.16.0](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v0.15.1...chrome-devtools-mcp-v0.16.0) (2026-02-04) ### 🎉 Features * include source-mapped stack trace for uncaught errors ([ChromeDevTools#876](ChromeDevTools#876)) ([ecef712](ChromeDevTools@ecef712)) ### 🛠️ Fixes * accidental extra typing in the fill tool ([ChromeDevTools#886](ChromeDevTools#886)) ([3d6e59d](ChromeDevTools@3d6e59d)) * update evaluateScript description formatting ([ChromeDevTools#880](ChromeDevTools#880)) ([24db9dd](ChromeDevTools@24db9dd)) * use 1-based line/column and fix wasm offsets in stack frames ([ChromeDevTools#884](ChromeDevTools#884)) ([7e1ec81](ChromeDevTools@7e1ec81)) ### 📄 Documentation * mention source-mapped stack traces in 'Key features' ([ChromeDevTools#883](ChromeDevTools#883)) ([579d18a](ChromeDevTools@579d18a)) * remove outdated --channel=beta note ([ChromeDevTools#882](ChromeDevTools#882)) ([acdb5c9](ChromeDevTools@acdb5c9)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note that we replace the existing "pageerror" handler with our new
UncaughtErrorhandler. The latter has a structured stack trace attached which we can source map via DevTools.This regresses the current functionality slightly, as we lose "pageerror"s for workers and oopif.