Module Resolution

[richb-rv]

Describe the bug
Seeing a module resolution bug implementing in Cursor, it looks like the package imports ES modules as named imports from what Node treats as CommonJS modules.

import {AgentFocus} from '../../node_modules/chrome-devtools-frontend/front_end/models/ai_assistance/performance/AIContext.js';
        ^^^^^^^^^^
SyntaxError: Named export 'AgentFocus' not found. The requested module '../../node_modules/chrome-devtools-frontend/front_end/models/ai_assistance/performance/AIContext.js' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from '../../node_modules/chrome-devtools-frontend/front_end/models/ai_assistance/performance/AIContext.js';
const {AgentFocus} = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:134:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:217:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:123:5)

To Reproduce
Steps to reproduce the behavior:

1. Add

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

to mcp file for Cursor

2. or run npx chrome-devtools-mcp@latest --help
3. See error

Expected behavior
MCP server has tools available

Chrome version: 140.0.7339.133
Coding agent version: latest
Node version: v20.16.0
Cursor version: v1.6.45

[vididvidid]

well i can't reproduce your bug.. mine is working perfectly..
i think you should do the
npx clear-npx-cache //clear the cache
npm install -g npm //upgrade the npm as in the readme of this repo its writter nodejs 22 or newer (your node version is 20)

[KarthikKadambi]

in the args try to explicitly point out to supported node version if you have multiple versions installed.. something like

export PATH=/Users//.nvm/versions/node/v22.18.0/bin:$PATH && npx chrome-devtools-mcp@latest .. that should resolve it

[fahmi-pdso]

I'm having the same issue, this wasn't even in the cursor

[vididvidid]

upgrade the node version and remove the cache then try again.. your node version is v20.. get the latest one.

[Mahdhir]

in the args try to explicitly point out to supported node version if you have multiple versions installed.. something like

export PATH=/Users//.nvm/versions/node/v22.18.0/bin:$PATH && npx chrome-devtools-mcp@latest .. that should resolve it

"chrome-devtools": {
      "command": "bash",
      "args": [
        "-c",
        "export PATH=/Users/myuser/.nvm/versions/node/v22.19.0/bin:$PATH && npx chrome-devtools-mcp@latest"
      ]
    }

Was able to add something like to vs code and got it working

[fahmi-pdso]

I see, the requirements also said we need node 22. Thank you for the solution, it should be safe to close this issue

[OrKoN]

Hi, thanks everyone for reporting the issue and sharing tips! chrome-devtools-mcp indeed requires Node 22+. Would it be possible for you to upgrade? We have a draft PR for Node 20 but it would require down-compilation to Node 20 because some of the DevTools code uses newer features that are not available in Node 20. With Node 20 being in the maintenance mode we decided for now not to support it. Let me know if it's not possible to upgrade to Node 22+ in your specific setup.

[ajasingh]

it works after upgrading the node version to v22.19.0