@lesscap/baton-cli 0.4.1 → 0.4.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lesscap/baton-cli",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "license": "MIT",
   "type": "module",
   "description": "baton CLI — register/run a worker, manage projects/requirements/tasks/sessions",

package/scripts/postinstall.mjs

@@ -1,16 +1,25 @@
-// Ensure node-pty's native addon actually loads after install. Its prebuilt
-// binaries don't cover every Node version (24/26 ship none, or a partial one that
-// installs without a working spawn-helper), so the bundle would crash the first
-// time a worker opens a terminal. If it won't load, rebuild it from source (needs
-// python3 + a C++ toolchain). Non-fatal: a worker that can't build it simply has
-// interactive terminals disabled, while the headless relay keeps working.
+// Ensure node-pty can actually spawn a pty after install. Its prebuilt binaries
+// are unreliable on newer Node (24/26 ship a partial one whose pty.node loads but
+// whose spawn-helper fails with `posix_spawnp failed`), so a plain require() isn't
+// a real check — spawn a throwaway pty. If that fails, rebuild from source (needs
+// python3 + a C++ toolchain). Non-fatal: a host that can't build it just loses
+// interactive terminals, while the headless relay keeps working.
 import { execSync } from 'node:child_process'
 import { createRequire } from 'node:module'
 
 const require = createRequire(import.meta.url)
-try {
-  require('node-pty')
-} catch {
+
+const works = () => {
+  try {
+    const pty = require('node-pty')
+    pty.spawn(process.platform === 'win32' ? 'cmd.exe' : '/bin/sh', [], { cols: 80, rows: 24 }).kill()
+    return true
+  } catch {
+    return false
+  }
+}
+
+if (!works()) {
   try {
     execSync('npm rebuild node-pty --build-from-source', { stdio: 'inherit' })
   } catch {