From 0ae5dd70cc28bdaf5a2cb894f8f2226e56e369a5 Mon Sep 17 00:00:00 2001 From: Alphons Jaimon Date: Thu, 27 Aug 2026 23:48:38 +0530 Subject: [PATCH] fix: bump node-pty to ^1.2.0-beta.12 so the plugin works on Linux MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit node-pty 1.1.0 ships prebuilt binaries only for darwin-arm64, darwin-x64, win32-arm64 and win32-x64 — there is no linux-x64 prebuild. Because semver ranges exclude prereleases, "^1.1.0" can never resolve to the 1.2.0-beta line that does ship Linux binaries. The result on Linux is that the plugin installs and builds fine, but the backend dies on startup: Error: [web-terminal] Cannot find module 'node-pty' Failed to start plugin server for web-terminal which surfaces in the UI as a Terminal tab that mounts but never connects. The underlying error is masked by the loader's generic re-throw; the real one is: Failed to load native module: pty.node, checked: build/Release, build/Debug, prebuilds/linux-x64: Cannot find module './prebuilds/linux-x64//pty.node' CloudCLI itself already depends on "^1.2.0-beta.12" for exactly this reason, so this change aligns the plugin with its host. Verified on Linux x64 / Node 22.18.0: a clean `npm install` resolves node-pty 1.2.0-beta.15, ships prebuilds/linux-x64/pty.node, requires without a source build, and `npm run build` succeeds. macOS and Windows are unaffected — the beta line ships their prebuilds too. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_011WfoF1z5anUFtH61ECn1ZF --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 2185558..567e09c 100644 --- a/package.json +++ b/package.json @@ -9,7 +9,7 @@ "dev": "tsc --watch" }, "dependencies": { - "node-pty": "^1.1.0", + "node-pty": "^1.2.0-beta.12", "ws": "^8.14.0" }, "devDependencies": {