@mesh-tech/mesh-cli 0.12.0 → 0.12.1

package/dist/bin/mesh.js

@@ -15459,15 +15459,67 @@ function shimScript() {
 # it. That resolves to bin/mesh.mjs, which runs the CLI from TypeScript source \u2014
 # so this always runs the LOCAL source of whatever worktree/app you are in, with
 # no build step. Nothing here is version-pinned; do not edit by hand.
+#
+# Outside a workspace it hands off to a globally installed mesh CLI (MESH-2869).
+# Without that hand-off the shim shadows \`npm i -g @mesh-tech/mesh-cli\` on the
+# PATH and \`mesh login\` is unreachable from the home directory \u2014 which is the
+# very first thing a new developer runs.
+# True when $1 is another copy of this shim. Reads the marker line with the
+# shell alone \u2014 no head/grep \u2014 so a stripped PATH cannot break the check.
+_mesh_is_shim() {
+  _n=0
+  while [ "$_n" -lt 6 ] && IFS= read -r _line; do
+    case $_line in *"canonical launcher shim"*) return 0 ;; esac
+    _n=$((_n + 1))
+  done < "$1"
+  return 1
+}
+
+# Walk up to the nearest workspace CLI. Parameter expansion, not \`dirname\`:
+# an unavailable dirname used to leave $dir empty and spin this loop forever.
 dir=$(pwd)
-while [ "$dir" != "/" ]; do
+while [ -n "$dir" ]; do
   if [ -x "$dir/node_modules/.bin/mesh" ]; then
     exec "$dir/node_modules/.bin/mesh" "$@"
   fi
-  dir=$(dirname "$dir")
+  [ "$dir" = "/" ] && break
+  parent=\${dir%/*}
+  [ -n "$parent" ] || parent=/
+  dir=$parent
+done
+
+# Not in a workspace: exec the next \`mesh\` on PATH that is not another copy of
+# this shim (matched on the marker line above, so we can never exec ourselves).
+self_dir=\${0%/*}
+[ "$self_dir" = "$0" ] && self_dir=.
+self_dir=$(CDPATH= cd -- "$self_dir" 2>/dev/null && pwd -P)
+saved_ifs=$IFS
+IFS=:
+set -f
+for entry in $PATH; do
+  IFS=$saved_ifs
+  set +f
+  [ -n "$entry" ] || entry=.
+  candidate=$entry/mesh
+  # -f as well as -x: [ -x ] is true for a DIRECTORY named mesh, which would be
+  # taken for the CLI and exec'd into a bare 126 without ever reaching the real
+  # one further down PATH. A shell's own PATH search skips directories.
+  if [ -f "$candidate" ] && [ -x "$candidate" ]; then
+    entry_dir=$(CDPATH= cd -- "$entry" 2>/dev/null && pwd -P)
+    if [ -n "$entry_dir" ] && [ "$entry_dir" != "$self_dir" ] && ! _mesh_is_shim "$candidate"; then
+      exec "$candidate" "$@"
+    fi
+  fi
+  IFS=:
+  set -f
 done
-echo "mesh: not inside a Mesh workspace (no node_modules/.bin/mesh found)." >&2
-echo "      cd into your app/repo (after 'pnpm install'), or run 'pnpm exec mesh'." >&2
+IFS=$saved_ifs
+set +f
+
+echo "mesh: not inside a Mesh workspace (no node_modules/.bin/mesh found)," >&2
+echo "      and no global mesh CLI found on PATH." >&2
+echo "      Install it:  npm i -g @mesh-tech/mesh-cli" >&2
+echo "      Or cd into your app/repo (after 'pnpm install') and use 'pnpm exec mesh'." >&2
 exit 1
 `;
 }