@rubytech/create-maxy-lite 0.1.10 → 0.1.12

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.
@@ -15,7 +15,7 @@
15
15
  // All external effects go through injected ctx primitives so the sequence,
16
16
  // guards and idempotency are unit-testable; index.mjs wires the real ones.
17
17
 
18
- import { PATHS, launcherPath, ptyLoadCommand } from './paths.mjs'
18
+ import { PATHS, launcherPath, ptyLoadCommand, GUEST_BUILD_ENV } from './paths.mjs'
19
19
 
20
20
  export const STEP_NAMES = ['termux-deps', 'proot', 'ubuntu', 'node', 'toolchain', 'vault-bind', 'npm-app']
21
21
 
@@ -95,8 +95,12 @@ const STEPS = [
95
95
  },
96
96
  {
97
97
  name: 'toolchain',
98
- done: (c) => c.runIn('command -v g++').code === 0,
99
- run: async (c) => ensureOk(await c.runInStream('apt install -y python3 make g++')),
98
+ // Detect + install under the clean Ubuntu env: with Termux's PATH scrubbed, the
99
+ // guard sees only the guest's tools, so it installs Ubuntu's make/g++ (and won't
100
+ // be fooled into skipping by Termux's g++ leaking through the inherited PATH).
101
+ // Verify make AND g++ — node-pty's node-gyp needs make, not just a compiler.
102
+ done: (c) => c.runIn(`${GUEST_BUILD_ENV}; command -v make >/dev/null && command -v g++ >/dev/null`).code === 0,
103
+ run: async (c) => ensureOk(await c.runInStream(`${GUEST_BUILD_ENV}; apt install -y python3 make g++`)),
100
104
  },
101
105
  {
102
106
  name: 'vault-bind',
package/lib/paths.mjs CHANGED
@@ -26,6 +26,17 @@ export const VALIDATOR_CLI = `${PATHS.appDir}/validator/cli.mjs`
26
26
  // exactly one place.
27
27
  export const PTY_NODE = `${WEBCHAT_DIR}/node_modules/node-pty/build/Release/pty.node`
28
28
 
29
+ // Clean guest environment for the native build / load / relay. The installer spawns
30
+ // proot FROM bare Termux, so the guest inherits Termux's PATH (its clang) and
31
+ // linker env (LD_LIBRARY_PATH/LD_PRELOAD → Termux's bionic libc + libc++_shared.so).
32
+ // Building node-pty under that linked it against Termux's libraries, so pty.node
33
+ // needed bionic `libc.so` (not found under glibc) — proven by `ldd` showing
34
+ // `libc++_shared.so => /data/data/com.termux/.../lib`. Forcing a clean Ubuntu PATH
35
+ // and dropping the leaked linker vars makes the build use Ubuntu's glibc toolchain,
36
+ // exactly as the spike's clean interactive login did.
37
+ export const GUEST_BUILD_ENV =
38
+ 'export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin; unset LD_LIBRARY_PATH LD_PRELOAD LIBRARY_PATH'
39
+
29
40
  /**
30
41
  * The guest-side command that proves node-pty's native module actually loads
31
42
  * 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.
36
47
  * binary (stale/wrong-ABI from a prior build) and wrongly skip the rebuild.
37
48
  */
38
49
  export function ptyLoadCommand({ webchatDir = WEBCHAT_DIR } = {}) {
39
- return `cd ${webchatDir} && node -e 'require("node-pty")'`
50
+ return `${GUEST_BUILD_ENV}; cd ${webchatDir} && node -e 'require("node-pty")'`
40
51
  }
41
52
 
42
53
  /**
@@ -51,7 +62,7 @@ export function ptyLoadCommand({ webchatDir = WEBCHAT_DIR } = {}) {
51
62
  * and the pass/fail gate) fails, to put the true reason into the step's `err=`.
52
63
  */
53
64
  export function ptyDirectLoadCommand({ ptyNode = PTY_NODE } = {}) {
54
- return `node -e 'require("${ptyNode}")'`
65
+ return `${GUEST_BUILD_ENV}; node -e 'require("${ptyNode}")'`
55
66
  }
56
67
 
57
68
  /**
@@ -74,7 +85,7 @@ export function webchatInstallCommand({ webchatDir = WEBCHAT_DIR } = {}) {
74
85
  // node_modules first, then install: that recreates the spike's empty-dir build.
75
86
  // `npm install node-pty` also resolves package.json (ws). The env prefix forces
76
87
  // scripts on to match the spike's environment regardless of ambient ignore-scripts.
77
- return `cd ${webchatDir} && rm -rf node_modules package-lock.json && npm_config_ignore_scripts=false npm install node-pty`
88
+ return `${GUEST_BUILD_ENV}; cd ${webchatDir} && rm -rf node_modules package-lock.json && npm_config_ignore_scripts=false npm install node-pty`
78
89
  }
79
90
 
80
91
  // The shipped skills, as bundled into the app dir, and the path the on-device
@@ -148,7 +159,7 @@ export function vaultBindLogin(
148
159
  inner,
149
160
  { distro = PATHS.distro, vaultHost = PATHS.vaultHost, vaultGuest = PATHS.vaultGuest } = {},
150
161
  ) {
151
- return `proot-distro login ${distro} --bind ${vaultHost}:${vaultGuest} -- bash -lc '${inner}'`
162
+ return `proot-distro login ${distro} --bind ${vaultHost}:${vaultGuest} -- bash -lc '${GUEST_BUILD_ENV}; ${inner}'`
152
163
  }
153
164
 
154
165
  /**
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rubytech/create-maxy-lite",
3
- "version": "0.1.10",
3
+ "version": "0.1.12",
4
4
  "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.",
5
5
  "type": "module",
6
6
  "engines": {