@rubytech/create-maxy-lite 0.1.9 → 0.1.11

package/index.mjs

@@ -136,27 +136,26 @@ const installDeps = async () => {
   // built artifact directly to recover the actual dlopen error, and carry THAT into
   // err= — the true reason (ABI/NODE_MODULE_VERSION/symbol/ELF), not the swallowed miss.
   if (runIn(ptyLoadCommand()).code !== 0) {
-    // proot emits `can't sanitize binding /proc/self/fd/*` lines on every
-    // non-interactive login; they are noise that buries the real error. Strip them.
-    const clean = (s) =>
+    // Build err= from the THREE facts that pin a native-load failure, each plainly
+    // labelled — not the raw multi-line Node stack (which buries the real line and
+    // truncates). `lines()` drops proot's per-login `can't sanitize binding` noise.
+    const lines = (s) =>
       String(s || '')
         .split('\n')
-        .filter((l) => !/proot warning: can't sanitize binding/.test(l))
-        .join(' ')
-        .replace(/\s+/g, ' ')
-        .trim()
+        .map((l) => l.trim())
+        .filter((l) => l && !/proot warning: can't sanitize binding/.test(l))
+    const join = (s) => lines(s).join(' ').replace(/\s+/g, ' ').trim()
+
+    // 1. The real error line only (e.g. `Error: libc.so: cannot open shared object
+    //    file`), not the dlopen stack frames.
     const direct = runIn(ptyDirectLoadCommand())
-    const cause = clean(direct.stderr) || `no stderr; ${PTY_NODE}`
-    // The load error is a libc-link failure (`libc.so: cannot open shared object
-    // file`). Capture which libraries pty.node actually needs (ldd) and any leaked
-    // Termux linker env (LD_*/LIBRARY_PATH) so the next run names the exact cause
-    // and we fix from certainty, not a guess.
-    const diag = runIn(
-      `ldd ${PTY_NODE} 2>&1; echo '|env:'; env | grep -iE 'LD_PRELOAD|LD_LIBRARY_PATH|LIBRARY_PATH' || echo '(no LD_* env)'`,
-    )
-    throw new Error(
-      `node-pty native module did not load after build: ${cause} || ldd+env: ${clean(diag.stdout + ' ' + diag.stderr)}`,
-    )
+    const errLine = lines(direct.stderr).find((l) => /Error:/.test(l)) || join(direct.stderr) || `no stderr; ${PTY_NODE}`
+    // 2. ldd: which shared objects pty.node needs and which resolve to "not found".
+    const ldd = join(runIn(`ldd ${PTY_NODE} 2>&1`).stdout)
+    // 3. Any leaked Termux linker env that could have steered the build's libc.
+    const env = join(runIn(`env | grep -iE 'LD_PRELOAD|LD_LIBRARY_PATH|LIBRARY_PATH' || echo '(no LD_* env)'`).stdout)
+
+    throw new Error(`node-pty did not load | error: ${errLine} | ldd: ${ldd} | env: ${env}`)
   }
 }
 

package/lib/paths.mjs

@@ -26,6 +26,17 @@ export const VALIDATOR_CLI = `${PATHS.appDir}/validator/cli.mjs`
 // exactly one place.
 export const PTY_NODE = `${WEBCHAT_DIR}/node_modules/node-pty/build/Release/pty.node`
 
+// Clean guest environment for the native build / load / relay. The installer spawns
+// proot FROM bare Termux, so the guest inherits Termux's PATH (its clang) and
+// linker env (LD_LIBRARY_PATH/LD_PRELOAD → Termux's bionic libc + libc++_shared.so).
+// Building node-pty under that linked it against Termux's libraries, so pty.node
+// needed bionic `libc.so` (not found under glibc) — proven by `ldd` showing
+// `libc++_shared.so => /data/data/com.termux/.../lib`. Forcing a clean Ubuntu PATH
+// and dropping the leaked linker vars makes the build use Ubuntu's glibc toolchain,
+// exactly as the spike's clean interactive login did.
+export const GUEST_BUILD_ENV =
+  'export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin; unset LD_LIBRARY_PATH LD_PRELOAD LIBRARY_PATH'
+
 /**
  * The guest-side command that proves node-pty's native module actually loads
  * under the guest's Node — `require("node-pty")` exits 0 only when `pty.node` is
@@ -36,7 +47,7 @@ export const PTY_NODE = `${WEBCHAT_DIR}/node_modules/node-pty/build/Release/pty.
  * binary (stale/wrong-ABI from a prior build) and wrongly skip the rebuild.
  */
 export function ptyLoadCommand({ webchatDir = WEBCHAT_DIR } = {}) {
-  return `cd ${webchatDir} && node -e 'require("node-pty")'`
+  return `${GUEST_BUILD_ENV}; cd ${webchatDir} && node -e 'require("node-pty")'`
 }
 
 /**
@@ -51,7 +62,7 @@ export function ptyLoadCommand({ webchatDir = WEBCHAT_DIR } = {}) {
  * and the pass/fail gate) fails, to put the true reason into the step's `err=`.
  */
 export function ptyDirectLoadCommand({ ptyNode = PTY_NODE } = {}) {
-  return `node -e 'require("${ptyNode}")'`
+  return `${GUEST_BUILD_ENV}; node -e 'require("${ptyNode}")'`
 }
 
 /**
@@ -74,7 +85,7 @@ export function webchatInstallCommand({ webchatDir = WEBCHAT_DIR } = {}) {
   // node_modules first, then install: that recreates the spike's empty-dir build.
   // `npm install node-pty` also resolves package.json (ws). The env prefix forces
   // scripts on to match the spike's environment regardless of ambient ignore-scripts.
-  return `cd ${webchatDir} && rm -rf node_modules package-lock.json && npm_config_ignore_scripts=false npm install node-pty`
+  return `${GUEST_BUILD_ENV}; cd ${webchatDir} && rm -rf node_modules package-lock.json && npm_config_ignore_scripts=false npm install node-pty`
 }
 
 // The shipped skills, as bundled into the app dir, and the path the on-device
@@ -148,7 +159,7 @@ export function vaultBindLogin(
   inner,
   { distro = PATHS.distro, vaultHost = PATHS.vaultHost, vaultGuest = PATHS.vaultGuest } = {},
 ) {
-  return `proot-distro login ${distro} --bind ${vaultHost}:${vaultGuest} -- bash -lc '${inner}'`
+  return `proot-distro login ${distro} --bind ${vaultHost}:${vaultGuest} -- bash -lc '${GUEST_BUILD_ENV}; ${inner}'`
 }
 
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy-lite",
-  "version": "0.1.9",
+  "version": "0.1.11",
   "description": "Install maxy-lite on an Android phone: orchestrates proot-distro Ubuntu, glibc Node, claude, the web-chat relay, the vault and its bind-mount — run via npx in bare Termux.",
   "type": "module",
   "engines": {