Skip to content

docs: fix contributor inspector build paths#2292

Open
CooperSheroy wants to merge 1 commit into
ChromeDevTools:mainfrom
CooperSheroy:catalina/contributing-inspector-paths-20260704
Open

docs: fix contributor inspector build paths#2292
CooperSheroy wants to merge 1 commit into
ChromeDevTools:mainfrom
CooperSheroy:catalina/contributing-inspector-paths-20260704

Conversation

@CooperSheroy

Copy link
Copy Markdown

Summary

  • update contributor inspector commands to use the checkout's built MCP binary instead of /build at filesystem root
  • clarify the MCP client config placeholder path so it includes the repository directory

Verification

  • npm ci
  • npm run build
  • npm run check-format
  • git diff --check
  • checked package.json bin path for chrome-devtools-mcp matches build/src/bin/chrome-devtools-mcp.js

Signed-off-by: CooperSheroy <sheroycoops@gmail.com>
@google-cla

google-cla Bot commented Jul 4, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@nattallius

Copy link
Copy Markdown
Contributor

Hi, in order for your pr to be merged, you need to sign cla.
And also your suggestion lacks support for win command line, so do can you update pr to reflect it?

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