Skip to content

Conversation

@jackfranklin
Copy link
Contributor

This PR tidies up the code around performance parsing and what we
respond with from our tools. It introduces the ability to have no
Insights from a trace (relatively rare, but can happen), and also adds
more information to the output in the event that something went wrong.

Previously we just logged errors, but if we respond with them here that
will also help users report issues and increase the chances that we can
debug them.

@jackfranklin jackfranklin requested a review from OrKoN September 23, 2025 13:02
This PR tidies up the code around performance parsing and what we
respond with from our tools. It introduces the ability to have no
Insights from a trace (relatively rare, but can happen), and also adds
more information to the output in the event that something went wrong.

Previously we just logged errors, but if we respond with them here that
will also help users report issues and increase the chances that we can
debug them.
@OrKoN OrKoN merged commit e8fb30c into main Sep 23, 2025
15 of 17 checks passed
@OrKoN OrKoN deleted the jackfr/noInsights branch September 23, 2025 13:42
OrKoN pushed a commit that referenced this pull request Sep 23, 2025
🤖 I have created a release *beep* *boop*
---


##
[0.2.2](chrome-devtools-mcp-v0.2.1...chrome-devtools-mcp-v0.2.2)
(2025-09-23)


### Bug Fixes

* cli version being reported as unknown
([#74](#74))
([d6bab91](d6bab91))
* remove unnecessary waiting for navigation
([#83](#83))
([924c042](924c042))
* rework performance parsing & error handling
([#75](#75))
([e8fb30c](e8fb30c))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants