@vib795/agent-memory 0.1.7 → 0.1.9

package/install.ps1

@@ -37,8 +37,25 @@ if (-not $node) {
 
 Write-Host ""
 Write-Host "Linking the CLI" -ForegroundColor Cyan
-& npm install -g $source 2>&1 | Out-Null
-if ($LASTEXITCODE -eq 0) {
+# npm writes its warnings to stderr, and `2>&1` turns each one into an ErrorRecord,
+# which $ErrorActionPreference = 'Stop' then treats as terminating. A managed npm
+# config makes that certain rather than unlikely: an unknown key such as `always-auth`
+# produces a warning on every single npm invocation, so this step could never succeed
+# on the desktops this script exists for. It aborted the whole install — no fallback
+# message, no doctor, no closing instructions — over a warning about an unrelated
+# config key. Scope the preference to this one call.
+$previousPreference = $ErrorActionPreference
+$ErrorActionPreference = 'Continue'
+try {
+    & npm install -g $source 2>&1 | Out-Null
+    $npmExit = $LASTEXITCODE
+} catch {
+    $npmExit = 1
+} finally {
+    $ErrorActionPreference = $previousPreference
+}
+
+if ($npmExit -eq 0) {
     Write-Host "  [npm] agent-memory installed globally" -ForegroundColor Green
 } else {
     # A global install failing on a managed desktop is common and not worth aborting

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vib795/agent-memory",
-  "version": "0.1.7",
+  "version": "0.1.9",
   "description": "Durable cross-repo knowledge graph for GitHub Copilot and Claude Code. Markdown source of truth, disposable SQLite index, zero runtime dependencies.",
   "keywords": [
     "github-copilot",

package/src/cli.js

@@ -565,7 +565,20 @@ function main(argv) {
   try {
     result = fn(opts);
   } catch (err) {
-    result = { ok: false, error: err.message, text: `Error: ${err.message}` };
+    // err.message on its own loses the syscall and the path, which is the whole
+    // difference between "Path is a directory" and knowing which path and which
+    // operation. A user hitting this on a machine you cannot log into should be able
+    // to paste one line and have it be enough; a stack is one env var further.
+    const detail = [err.code, err.syscall, err.path].filter(Boolean).join(' ');
+    const line = detail ? `Error: ${err.message} [${detail}]` : `Error: ${err.message}`;
+    result = {
+      ok: false,
+      error: err.message,
+      code: err.code ?? null,
+      syscall: err.syscall ?? null,
+      path: err.path ?? null,
+      text: process.env.AGENT_MEMORY_DEBUG ? `${line}\n${err.stack}` : line,
+    };
   }
 
   if (opts.json) {

package/src/setup.js

@@ -1,5 +1,5 @@
 import {
-  mkdirSync, rmSync, existsSync, lstatSync, symlinkSync, cpSync, readlinkSync, readFileSync,
+  mkdirSync, rmSync, rmdirSync, existsSync, lstatSync, symlinkSync, cpSync, readlinkSync, readFileSync,
 } from 'node:fs';
 import { join, dirname, resolve } from 'node:path';
 import { fileURLToPath } from 'node:url';
@@ -45,8 +45,19 @@ function isLink(path) {
 function clear(path) {
   // A stale symlink must be removed as a link rather than followed, or clearing it
   // would delete the packaged skills on the other end.
-  if (isLink(path)) rmSync(path, { force: true });
-  else if (existsSync(path)) rmSync(path, { recursive: true, force: true });
+  if (isLink(path)) {
+    try {
+      rmSync(path, { force: true });
+    } catch {
+      // A Windows directory junction reports as a symbolic link but deletes like a
+      // directory, and rmSync without `recursive` can reject it as EISDIR. rmdirSync
+      // removes the junction itself and never descends, so the skills on the other
+      // end stay put — which is exactly what passing `recursive` here would risk.
+      rmdirSync(path);
+    }
+  } else if (existsSync(path)) {
+    rmSync(path, { recursive: true, force: true });
+  }
 }
 
 /**