v0.17.2 npm package is missing build directory — cannot start

[9c5s]

Description of the bug

v0.17.2 published to npm is missing the entire build/ directory. The package contains only 3 files (LICENSE, README.md, package.json), so the entry point build/src/index.js cannot be resolved. This is the same class of issue as #324.

Reproduction

$ npm pack chrome-devtools-mcp@0.17.2 --dry-run
npm notice 📦  chrome-devtools-mcp@0.17.2
npm notice Tarball Contents
npm notice 11.4kB LICENSE
npm notice 26.9kB README.md
npm notice 3.3kB  package.json
npm notice total files: 3

vs working v0.17.1:

$ npm pack chrome-devtools-mcp@0.17.1 --dry-run
npm notice 📦  chrome-devtools-mcp@0.17.1
npm notice Tarball Contents
npm notice 11.4kB  LICENSE
npm notice 26.8kB  README.md
npm notice 6.4kB   build/src/browser.js
npm notice 11.3kB  build/src/cli.js
npm notice 2.6kB   build/src/DevToolsConnectionAdapter.js
npm notice 13.2kB  build/src/DevtoolsUtils.js
...

Running v0.17.2 produces:

Error: Cannot find module '.../chrome-devtools-mcp/build/src/index.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1448:15)

Expectation

The build/src/ directory should be included in the published npm package, as it is in v0.17.1 and all prior working versions.

MCP configuration

{
  "chrome-devtools": {
    "type": "stdio",
    "command": "npx",
    "args": ["-y", "chrome-devtools-mcp@latest"]
  }
}

Chrome DevTools MCP version

0.17.2

Node version

v24.3.0

Operating system

Windows

Workaround

Pin to v0.17.1:

npx -y chrome-devtools-mcp@0.17.1

[OrKoN]

Thanks for reporting and sorry for the trouble. The fix will be out shortly.

[OrKoN]

0.17.3 is published

[9c5s]

Thank you for your prompt response. I rely on this useful tool all the time.