@yezack/chrome-devtools-mcp-108 1.10.2 → 1.10.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/FORK-NOTICE.md +17 -2
- package/README.md +9 -2
- package/build/src/version.js +1 -1
- package/package.json +1 -1
package/FORK-NOTICE.md
CHANGED
|
@@ -12,8 +12,10 @@ team. For the official package use `chrome-devtools-mcp`.
|
|
|
12
12
|
Base: upstream tag `chrome-devtools-mcp-v1.10.1` (puppeteer-core 25.11.0),
|
|
13
13
|
taken from the published npm tarball.
|
|
14
14
|
|
|
15
|
-
Modified
|
|
16
|
-
appended to the same module).
|
|
15
|
+
Modified files: `build/src/third_party/index.js` (one code path, plus one
|
|
16
|
+
helper appended to the same module) and `build/src/BrowserManager.js`.
|
|
17
|
+
|
|
18
|
+
### 1. Page discovery on Chrome 108-110
|
|
17
19
|
|
|
18
20
|
Upstream initialises target discovery with:
|
|
19
21
|
|
|
@@ -36,6 +38,19 @@ This fork wraps that one call site in
|
|
|
36
38
|
111, removes `filter`. Those browsers then attach page targets directly, which
|
|
37
39
|
puppeteer handles correctly. Browsers 111 and newer are passed through unchanged.
|
|
38
40
|
|
|
41
|
+
### 2. Temporary profile by default
|
|
42
|
+
|
|
43
|
+
Upstream launches with a persistent user-data-dir at
|
|
44
|
+
`$HOME/.cache/chrome-devtools-mcp/chrome-profile` and creates it with `mkdir`
|
|
45
|
+
before launching. On a host where the home directory is a read-only mount that
|
|
46
|
+
fails with `EROFS`/`EPERM`, and the failure surfaces through every page tool
|
|
47
|
+
(`list_pages` returned that mkdir error). This fork defaults to an isolated
|
|
48
|
+
temporary profile instead (under the OS temp directory, e.g. `$TMPDIR` on
|
|
49
|
+
Linux), which is what the upstream CLI entry point already did. The default is
|
|
50
|
+
applied as a destructuring default rather than a yargs default, so
|
|
51
|
+
`--user-data-dir <path>` still wins the conflict resolution. `--no-isolated`
|
|
52
|
+
restores the upstream behaviour.
|
|
53
|
+
|
|
39
54
|
Verified against Chromium 108.0.5351.0 (snapshot r1056772) and
|
|
40
55
|
Chrome 154.0.8037.99.
|
|
41
56
|
|
package/README.md
CHANGED
|
@@ -6,8 +6,15 @@ that also works against **Chrome/Chromium 108-110**.
|
|
|
6
6
|
The upstream package requires Chrome 111+ for page discovery: on Chrome 108 the
|
|
7
7
|
connection-level `Target.setAutoAttach` filter suppresses every target, so
|
|
8
8
|
`list_pages` returns an empty array. This fork removes that filter on browsers
|
|
9
|
-
older than 111
|
|
10
|
-
|
|
9
|
+
older than 111.
|
|
10
|
+
|
|
11
|
+
It also defaults to an isolated temporary profile under the OS temp directory
|
|
12
|
+
instead of `$HOME/.cache/chrome-devtools-mcp`, so it starts on hosts whose home
|
|
13
|
+
directory is a read-only mount. Pass `--no-isolated` for the persistent
|
|
14
|
+
upstream profile, or `--user-data-dir <path>` to choose a specific one.
|
|
15
|
+
|
|
16
|
+
Otherwise this fork is identical to upstream 1.10.1. See
|
|
17
|
+
[FORK-NOTICE.md](./FORK-NOTICE.md) for the exact changes and the evidence.
|
|
11
18
|
|
|
12
19
|
## Usage
|
|
13
20
|
|
package/build/src/version.js
CHANGED
package/package.json
CHANGED