@dreamdata_io/verify-tracking 0.1.1 → 0.1.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dreamdata_io/verify-tracking",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Scrapes a live website with Playwright and asks an AI model whether the Dreamdata Analytics Script is correctly installed.",
   "type": "module",
   "license": "MIT",

package/scripts/install.sh

@@ -327,22 +327,93 @@ else
 fi
 
 # ---------------------------------------------------------------------------
-# Done
+# 7. PATH
 # ---------------------------------------------------------------------------
 
-printf '\n==> Installed\n'
-"$BIN_DIR/verify-tracking" --version 2>/dev/null | sed 's/^/  /' || true
+# Appended for the operator rather than printed for them to paste. The people
+# this installer is for do not know what a shell profile is, and "now edit
+# ~/.zshrc" is the second place a handover stops.
+#
+# Every profile that already exists gets the line, not just the one implied by
+# $SHELL: a macOS login shell reads ~/.zprofile, an interactive one ~/.zshrc,
+# and bash reads ~/.bash_profile rather than ~/.bashrc — guessing a single file
+# is how the line lands somewhere that is never sourced. A file that does not
+# exist is left uncreated, so this never conjures a profile for a shell the
+# machine does not use.
+#
+# What it cannot do is take effect in the terminal that ran it: this script is
+# a child process, and no child can alter its parent's environment. So the
+# closing lines send the operator to a new terminal window rather than letting
+# them discover that on a `command not found`.
+PATH_LINE="export PATH=\"$BIN_DIR:\$PATH\""
+# BIN_DIR is a path, and a path is not a regex: an unescaped `.` in `.local`
+# would match any character, so a near-miss line could read as a hit. The class
+# is the full ERE metacharacter set, not just the BRE one — grep runs with -E,
+# and a home directory is free to contain a `+` or a `(`.
+bin_dir_re="$(printf '%s' "$BIN_DIR" | sed 's/[].[^$*+?(){}|\/\\]/\\&/g')"
+
+add_to_profile() {
+  profile="$1"
+  [ -f "$profile" ] || return 0
+  # Anchored, and only on an uncommented line: a commented-out or
+  # differently-worded mention must not read as "already configured". BIN_DIR
+  # has to end a PATH component too — as a bare substring, `~/.local/bin` is
+  # also inside `~/.local/bin2`, and a match there would skip a profile that
+  # never had the line.
+  if grep -Eq "^[[:space:]]*export[[:space:]]+PATH=.*${bin_dir_re}([:\"']|\$)" "$profile"; then
+    say "already in $profile"
+    return 0
+  fi
+  # A profile that cannot be written to is a PATH the operator has to set by
+  # hand, not a failed install — under `set -e` an unguarded append would take
+  # the whole run down over a read-only home.
+  if printf '\n# Added by the verify-tracking installer\n%s\n' "$PATH_LINE" >> "$profile" 2>/dev/null; then
+    say "added to $profile"
+  else
+    say "could not write $profile. Add this line to it yourself:"
+    printf '\n    %s\n' "$PATH_LINE"
+  fi
+}
 
+step "PATH"
 case ":${PATH}:" in
-  *":$BIN_DIR:"*) ;;
+  *":$BIN_DIR:"*)
+    say "$BIN_DIR is already on your PATH"
+    ;;
   *)
-    printf '\n  %s is not on your PATH. Add it, then reopen your terminal:\n\n' "$BIN_DIR"
-    printf "    echo 'export PATH=\"%s:\$PATH\"' >> ~/.zshrc\n" "$BIN_DIR"
+    for profile in "$HOME/.zshrc" "$HOME/.zprofile" "$HOME/.bashrc" "$HOME/.bash_profile"; do
+      add_to_profile "$profile"
+    done
+    # Nothing to append to means nothing was appended — print the line rather
+    # than claim a PATH change that did not happen.
+    if [ -f "$HOME/.zshrc" ] || [ -f "$HOME/.zprofile" ] \
+       || [ -f "$HOME/.bashrc" ] || [ -f "$HOME/.bash_profile" ]; then
+      :
+    else
+      say "no shell profile found. Add this line to yours:"
+      printf '\n    %s\n' "$PATH_LINE"
+    fi
     ;;
 esac
 
+# ---------------------------------------------------------------------------
+# Done
+# ---------------------------------------------------------------------------
+
+printf '\n==> Installed\n'
+"$BIN_DIR/verify-tracking" --version 2>/dev/null | sed 's/^/  /' || true
+
 printf '\n  Reports and dashboard:\n\n    %s\n' "$REPORTS_HOME"
-printf '\n  Try it:\n\n    verify-tracking --slug dreamdata_io --url https://dreamdata.io/\n'
+printf '\n  Try it, from a new terminal window:\n\n    verify-tracking --slug dreamdata_io --url https://dreamdata.io/\n'
+
+# Claimed only where a browser can actually appear: --dashboard skips opening
+# one on a machine with nobody in front of it, and an installer that announces
+# a window that never arrives sends the operator looking for it.
+if [ -r /dev/tty ]; then
+  printf '\n  A browser window is opening with your dashboard. Type an account slug\n'
+  printf '  and a URL there to build your command, then open a new terminal window\n'
+  printf '  and run it.\n'
+fi
 # The reports folder is the operator's data and is deliberately left out: an
 # `rm -rf` line someone pastes without reading must not take their work with it.
 printf '\n  Uninstall (your reports folder is left in place):\n\n    rm -rf %s %s/verify-tracking %s/verify-tracking-mcp\n\n' "$PREFIX" "$BIN_DIR" "$BIN_DIR"