claude-multiacc 2.0.4 → 2.0.5

package/bin/claude-accounts

@@ -2351,6 +2351,15 @@ cmd_self_update() {
         ulog "self-update: no npm found (looked in $prefix/bin, /opt/homebrew/bin, /usr/local/bin, /usr/bin, PATH); skipping"
         return 0
       }
+      # Finding npm is not the same as being able to RUN it: npm ships as
+      # `#!/usr/bin/env node`, so an agent PATH without the node that owns it makes
+      # every invocation die with "env: node: No such file or directory" — and npm
+      # exits 0 on that, so the version probe just came back empty and the update
+      # "failed" with nothing to explain it. node lives beside npm, so every npm call
+      # below runs with that directory in front (command-scoped: nothing else in this
+      # process has its PATH changed underneath it).
+      local npm_path
+      npm_path="$(dirname "$npm_bin"):$PATH"
       # Update THE COPY THAT IS RUNNING, not whichever one the ambient npm prefix
       # happens to point at. my-mini had two global installs — homebrew's on PATH and
       # nvm's under `npm root -g` — and self-update kept upgrading the nvm one and
@@ -2359,13 +2368,13 @@ cmd_self_update() {
       # A deploy nobody runs is not a deploy, and one that announces success is worse
       # than one that fails.
       cur="$(pkg_version_at "$REPO_DIR")"
-      lat="$("$npm_bin" view claude-multiacc version 2>/dev/null)"
+      lat="$(PATH="$npm_path" "$npm_bin" view claude-multiacc version 2>/dev/null)"
       if [ -n "$lat" ] && [ "$cur" = "$lat" ]; then
         ulog "self-update: already latest ($cur)"
         return 0
       fi
       ulog "self-update: npm $cur -> ${lat:-latest} (prefix $prefix, npm $npm_bin)"
-      if "$npm_bin" install -g --prefix "$prefix" claude-multiacc@latest \
+      if PATH="$npm_path" "$npm_bin" install -g --prefix "$prefix" claude-multiacc@latest \
            >>"$ACC_ROOT/update.log" 2>&1; then
         # Verify by re-reading the file on disk. npm reporting success says nothing
         # about which tree it wrote to.

package/bin/codex-accounts

@@ -1899,14 +1899,23 @@ cmd_self_update() {
         ulog "self-update: no npm found (looked in $prefix/bin, /opt/homebrew/bin, /usr/local/bin, /usr/bin, PATH); skipping"
         return 0
       }
+      # Finding npm is not the same as being able to RUN it: npm ships as
+      # `#!/usr/bin/env node`, so an agent PATH without the node that owns it makes
+      # every invocation die with "env: node: No such file or directory" — and npm
+      # exits 0 on that, so the version probe just came back empty and the update
+      # "failed" with nothing to explain it. node lives beside npm, so every npm call
+      # below runs with that directory in front (command-scoped: nothing else in this
+      # process has its PATH changed underneath it).
+      local npm_path
+      npm_path="$(dirname "$npm_bin"):$PATH"
       cur="$(pkg_version_at "$REPO_DIR")"
-      lat="$("$npm_bin" view claude-multiacc version 2>/dev/null)"
+      lat="$(PATH="$npm_path" "$npm_bin" view claude-multiacc version 2>/dev/null)"
       if [ -n "$lat" ] && [ "$cur" = "$lat" ]; then
         ulog "self-update: already latest ($cur)"
         return 0
       fi
       ulog "self-update: npm $cur -> ${lat:-latest} (prefix $prefix, npm $npm_bin)"
-      if "$npm_bin" install -g --prefix "$prefix" claude-multiacc@latest \
+      if PATH="$npm_path" "$npm_bin" install -g --prefix "$prefix" claude-multiacc@latest \
            >>"$ACC_ROOT/update.log" 2>&1; then
         after="$(pkg_version_at "$REPO_DIR")"
         if [ -n "$lat" ] && [ "$after" != "$lat" ]; then

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-multiacc",
-  "version": "2.0.4",
+  "version": "2.0.5",
   "description": "Unified Claude Code and OpenAI Codex subscription pooling with quota-aware selection.",
   "type": "module",
   "bin": {

package/tests/run-tests.sh

@@ -2451,8 +2451,17 @@ if command -v node >/dev/null 2>&1; then
     mkdir -p "$NPMROOT" "$PFX/bin"
     cp -R "$REPO_DIR/bin" "$REPO_DIR/lib" "$REPO_DIR/package.json" "$NPMROOT/"
     # A fake npm that records how it was called and "installs" by bumping package.json.
-    cat > "$PFX/bin/npm" <<NPMEOF
+    # Its shebang names an interpreter that exists ONLY beside it, mirroring the real
+    # npm's `#!/usr/bin/env node`: resolving npm by absolute path is not enough if the
+    # agent's PATH cannot find npm's own interpreter, which is how the update failed
+    # with an empty version probe and no explanation.
+    cat > "$PFX/bin/multiacc-fake-node" <<'NODEEOF'
 #!/usr/bin/env bash
+exec /bin/bash "$@"
+NODEEOF
+    chmod +x "$PFX/bin/multiacc-fake-node"
+    cat > "$PFX/bin/npm" <<NPMEOF
+#!/usr/bin/env multiacc-fake-node
 echo "npm \$*" >> "$WORK/npm-calls-$_cli.log"
 case "\${1:-}" in
   view) echo 9.9.9 ;;
@@ -2488,6 +2497,9 @@ NPMEOF
       && t_fail "$_cli npm choice" "used the npm from PATH instead of the running prefix's" \
       || t_ok "$_cli: a stray npm on PATH never wins over the running prefix's"
     check "$_cli: self-update verifies the tree it wrote" "npm update ok (9.9.9)" "$out"
+    grep -q "^npm view " "$WORK/npm-calls-$_cli.log" \
+      && t_ok "$_cli: npm ran despite its interpreter being off PATH" \
+      || t_fail "$_cli npm interpreter" "npm never executed — its shebang interpreter was not found"
   done
   # The agents install.sh writes must carry a PATH for the same reason (a future tool
   # that is not resolved by absolute path would hit exactly this again).