8e90a92780
chore: split withBrowser into withBrowser and withMcpContext ( #620 )
...
I split this PR off from my "create one DevTools universe per page" PR
in preparation. This allows tests to re-use browser instances without
creating an `McpContext`.
Drive-by: Move mocked browser/page into utils.ts.
2025-11-28 07:52:52 +01:00
94752ffade
fix: prevent dropping license notices on some files when publishing ( #604 )
...
This PR prevents license notices being dropped when creating package for
publication.
This can happen when first import in the file is type-only import that
gets removed during build. When there is no empty line between the
license block comment and such import, the comment is treated as related
to the import and gets removed alongside it.
Adding an empty line between copyright notice and the import fixes the
issue.
Co-authored-by: Piotr Paulski <piotrpaulski@chromium.org >
2025-11-24 12:38:30 +00:00
247e1b6a71
chore(deps-dev): bump chrome-devtools-frontend from 1.0.1539728 to 1.0.1541169 in the bundled-devtools group ( #536 )
...
Bumps the bundled-devtools group with 1 update:
[chrome-devtools-frontend](https://github.com/ChromeDevTools/devtools-frontend ).
Updates `chrome-devtools-frontend` from 1.0.1539728 to 1.0.1541169
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/ChromeDevTools/devtools-frontend/commit/393435aef80c8bff3fa7ed835992704ea5a7339e "><code>393435a</code></a>
Update Chrome (for Testing) PIN</li>
<li><a
href="https://github.com/ChromeDevTools/devtools-frontend/commit/59cc38b28a0697eb6908ba9e6c2502edb08fe349 "><code>59cc38b</code></a>
Update DevTools DEPS (trusted)</li>
<li><a
href="https://github.com/ChromeDevTools/devtools-frontend/commit/67a631561ba193aaf72303215d5ef5bd2def4811 "><code>67a6315</code></a>
[RPP] Simplify insight set id</li>
<li><a
href="https://github.com/ChromeDevTools/devtools-frontend/commit/941f21add00a7a522cb5dfa13c99b032f3c782be "><code>941f21a</code></a>
[AI] Present trace facts grouped by insight set</li>
<li><a
href="https://github.com/ChromeDevTools/devtools-frontend/commit/8ae5a850eb98c42fd882dab3a59115e6f2d6a8ef "><code>8ae5a85</code></a>
Revert from <code>fetch</code> back to <code>http.request</code> in
resultsdb.ts</li>
<li><a
href="https://github.com/ChromeDevTools/devtools-frontend/commit/774cfe78fe219714e5d89354d7815ac91342dc2a "><code>774cfe7</code></a>
Update Chrome (for Testing) PIN</li>
<li><a
href="https://github.com/ChromeDevTools/devtools-frontend/commit/76cbb2c5b1627eb6903b8ad9f8a93ef77f442ed9 "><code>76cbb2c</code></a>
[eslint] Add <code>eslint-plugin-lit</code></li>
<li><a
href="https://github.com/ChromeDevTools/devtools-frontend/commit/92be0b6fde17878efced6c91330b29b3adefe6a9 "><code>92be0b6</code></a>
Replace <code>outline-width: 0</code> with <code>outline-style:
none</code></li>
<li><a
href="https://github.com/ChromeDevTools/devtools-frontend/commit/fa72d9702d35727a48d567a67df26a23e6e2ef74 "><code>fa72d97</code></a>
Move affected count updates out of list rendering</li>
<li><a
href="https://github.com/ChromeDevTools/devtools-frontend/commit/baec26cf66c7dae30594b4a03f696fb3f17fa337 "><code>baec26c</code></a>
Roll browser-protocol</li>
<li>Additional commits viewable in <a
href="https://github.com/ChromeDevTools/devtools-frontend/compare/v1.0.1539728...v1.0.1541169 ">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores )
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions
</details>
---------
Signed-off-by: dependabot[bot] <support@github.com >
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Alex Rudenko <alexrudenko@chromium.org >
2025-11-10 14:23:08 +00:00
36504d29ca
feat: add insightSetId to performance_analyze_insight ( #518 )
...
This should land with / after
https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/508
2025-11-04 08:18:04 +00:00
8200194c80
fix: guard performance_stop_trace when tracing inactive ( #295 )
...
PR Description
- Fix the stop-trace guard to call context.isRunningPerformanceTrace()
so we skip page.tracing.stop() when nothing is recording, avoiding the
Puppeteer error that bubbled up
to users.
- Extend the “does nothing” test to stub tracing.stop() and assert it
stays untouched, guaranteeing the guard path is covered.
2025-10-07 12:04:41 +00:00
15277541d8
chore: add additional EsLint rule ( #147 )
2025-09-25 17:20:01 +02:00
adfcecf987
fix: validate and report incompatible Node versions ( #113 )
...
Ref https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/92
2025-09-24 14:45:27 +02:00
e8fb30c1bf
fix: rework performance parsing & error handling ( #75 )
...
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.
2025-09-23 15:42:35 +02:00
21e175b862
feat: add performance_analyze_insight tool. ( #42 )
2025-09-17 12:25:40 +00:00
31a0bdce26
feat: initial version
2025-09-11 12:46:05 +02:00
Simon Zünd