@yezack/chrome-devtools-mcp-108 1.10.2 → 1.10.4

package/FORK-NOTICE.md

@@ -12,8 +12,11 @@ team. For the official package use `chrome-devtools-mcp`.
 Base: upstream tag `chrome-devtools-mcp-v1.10.1` (puppeteer-core 25.11.0),
 taken from the published npm tarball.
 
-Modified file: `build/src/third_party/index.js` (one code path, plus one helper
-appended to the same module).
+Modified files: `build/src/third_party/index.js` (one code path, plus one
+helper appended to the same module), `build/src/BrowserManager.js` and
+`build/src/utils/check-for-updates.js`.
+
+### 1. Page discovery on Chrome 108-110
 
 Upstream initialises target discovery with:
 
@@ -36,6 +39,29 @@ This fork wraps that one call site in
 111, removes `filter`. Those browsers then attach page targets directly, which
 puppeteer handles correctly. Browsers 111 and newer are passed through unchanged.
 
+### 2. Temporary profile by default
+
+Upstream launches with a persistent user-data-dir at
+`$HOME/.cache/chrome-devtools-mcp/chrome-profile` and creates it with `mkdir`
+before launching. On a host where the home directory is a read-only mount that
+fails with `EROFS`/`EPERM`, and the failure surfaces through every page tool
+(`list_pages` returned that mkdir error). This fork defaults to an isolated
+temporary profile instead (under the OS temp directory, e.g. `$TMPDIR` on
+Linux), which is what the upstream CLI entry point already did. The default is
+applied as a destructuring default rather than a yargs default, so
+`--user-data-dir <path>` still wins the conflict resolution. `--no-isolated`
+restores the upstream behaviour.
+
+### 3. Update-check cache location
+
+The update check cached the latest version in a hardcoded
+`$HOME/.cache/chrome-devtools-mcp/latest.json` (20 bytes), independent of the
+profile setting, so a read-only home still received a write attempt on every
+start. It now picks the first writable directory out of
+`$HOME/.cache/chrome-devtools-mcp` and `$TMPDIR/chrome-devtools-mcp`: normal
+hosts keep the upstream location, read-only homes fall back to the OS temp
+directory. `CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS=1` skips the check entirely.
+
 Verified against Chromium 108.0.5351.0 (snapshot r1056772) and
 Chrome 154.0.8037.99.
 

package/README.md

@@ -6,8 +6,15 @@ that also works against **Chrome/Chromium 108-110**.
 The upstream package requires Chrome 111+ for page discovery: on Chrome 108 the
 connection-level `Target.setAutoAttach` filter suppresses every target, so
 `list_pages` returns an empty array. This fork removes that filter on browsers
-older than 111 and is otherwise identical to upstream 1.10.1. See
-[FORK-NOTICE.md](./FORK-NOTICE.md) for the exact change and the evidence.
+older than 111.
+
+It also defaults to an isolated temporary profile under the OS temp directory
+instead of `$HOME/.cache/chrome-devtools-mcp`, so it starts on hosts whose home
+directory is a read-only mount. Pass `--no-isolated` for the persistent
+upstream profile, or `--user-data-dir <path>` to choose a specific one.
+
+Otherwise this fork is identical to upstream 1.10.1. See
+[FORK-NOTICE.md](./FORK-NOTICE.md) for the exact changes and the evidence.
 
 ## Usage
 

package/build/src/utils/check-for-updates.js

@@ -24,7 +24,7 @@ export async function checkForUpdates(message) {
         return;
     }
     isChecking = true;
-    const cachePath = path.join(os.homedir(), '.cache', 'chrome-devtools-mcp', 'latest.json');
+    const cachePath = path.join(await __dshWritableDir([path.join(os.homedir(), '.cache', 'chrome-devtools-mcp'), path.join(os.tmpdir(), 'chrome-devtools-mcp')]), 'latest.json');
     let cachedVersion;
     let stats;
     try {
@@ -72,4 +72,17 @@ export async function checkForUpdates(message) {
         // Fail silently in case of any errors.
     }
 }
-//# sourceMappingURL=check-for-updates.js.map
+//# sourceMappingURL=check-for-updates.js.map
+
+async function __dshWritableDir(candidates) {
+    for (const dir of candidates) {
+        try {
+            await fs.mkdir(dir, {recursive: true});
+            return dir;
+        }
+        catch {
+            // Not writable (for example a read-only home directory).
+        }
+    }
+    return candidates[candidates.length - 1];
+}

package/build/src/version.js

@@ -5,6 +5,6 @@
  */
 // If moved update release-please config
 // x-release-please-start-version
-export const VERSION = '1.10.1';
+export const VERSION = '1.10.4';
 // x-release-please-end
 //# sourceMappingURL=version.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yezack/chrome-devtools-mcp-108",
-  "version": "1.10.2",
+  "version": "1.10.4",
   "description": "Unofficial fork of chrome-devtools-mcp with Chrome/Chromium 108-110 (legacy TargetFilter) support",
   "type": "module",
   "bin": {