Conversation
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 10, 2026
🤖 I have created a release *beep* *boop* --- ## [0.17.0](chrome-devtools-mcp-v0.16.0...chrome-devtools-mcp-v0.17.0) (2026-02-10) ### 🎉 Features * include Error.cause chain for uncaught errors and logged Errors ([#906](#906)) ([05b01ec](05b01ec)) * Integrate CrUX data into performance trace summaries ([#733](#733)) ([b747f9d](b747f9d)) * show message and stack trace in details when console.log'ging Error objects ([#902](#902)) ([ffa00da](ffa00da)) ### 🛠️ Fixes * console formatter hides frames from ignored scripts ([#927](#927)) ([8e2380b](8e2380b)) * limit stack traces to 50 lines ([#923](#923)) ([caea23a](caea23a)) ### 📄 Documentation * add macOS Web Bluetooth troubleshooting note ([#930](#930)) ([3c9528b](3c9528b)), closes [#917](#917) --- 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
This PR refactors the stack trace formatting logic a bit: We split the `formatStackTrace` function into 2: One for the top-level stack trace and the rest for the recursive ones. We also return lines separately so we can slice the result later.
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.17.0](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v0.16.0...chrome-devtools-mcp-v0.17.0) (2026-02-10) ### 🎉 Features * include Error.cause chain for uncaught errors and logged Errors ([ChromeDevTools#906](ChromeDevTools#906)) ([05b01ec](ChromeDevTools@05b01ec)) * Integrate CrUX data into performance trace summaries ([ChromeDevTools#733](ChromeDevTools#733)) ([b747f9d](ChromeDevTools@b747f9d)) * show message and stack trace in details when console.log'ging Error objects ([ChromeDevTools#902](ChromeDevTools#902)) ([ffa00da](ChromeDevTools@ffa00da)) ### 🛠️ Fixes * console formatter hides frames from ignored scripts ([ChromeDevTools#927](ChromeDevTools#927)) ([8e2380b](ChromeDevTools@8e2380b)) * limit stack traces to 50 lines ([ChromeDevTools#923](ChromeDevTools#923)) ([caea23a](ChromeDevTools@caea23a)) ### 📄 Documentation * add macOS Web Bluetooth troubleshooting note ([ChromeDevTools#930](ChromeDevTools#930)) ([3c9528b](ChromeDevTools@3c9528b)), closes [ChromeDevTools#917](ChromeDevTools#917) --- 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.
This PR refactors the stack trace formatting logic a bit: We split the
formatStackTracefunction into 2: One for the top-level stack trace and the rest for the recursive ones. We also return lines separately so we can slice the result later.