@vib795/agent-memory 0.1.6 → 0.1.8

package/HOWTO.md

@@ -70,11 +70,14 @@ agent-memory setup
 you have. Modern npm refuses to let a package run its own setup automatically — a
 sensible security default — so the second line is you giving permission, by hand.
 
-> No access to the npm registry at work? This works too, and needs nothing but GitHub:
+> No access to the npm registry at work? Clone it instead. This needs nothing but
+> GitHub, and it is what to use if your company proxy blocks or quarantines npm:
 > ```bash
-> npm install -g https://github.com/vib795/agent-memory.git
+> git clone https://github.com/vib795/agent-memory.git
+> npm install -g ./agent-memory
 > agent-memory setup
 > ```
+> Clone first — installing from the git URL directly does not work. See the README.
 
 ### What just happened
 

package/README.md

@@ -182,13 +182,20 @@ npm install -g @vib795/agent-memory
 agent-memory setup
 ```
 
-Straight from git works too, and needs no registry access:
+No registry access? Clone it and install the directory. This needs nothing but
+GitHub, and it is the path to use behind a proxy that blocks or quarantines npm:
 
 ```bash
-npm install -g https://github.com/vib795/agent-memory.git
+git clone https://github.com/vib795/agent-memory.git
+npm install -g ./agent-memory
 agent-memory setup
 ```
 
+**Do not install from the git URL directly.** `npm install -g <git-url>` fails for
+this package: npm links the package into `~/.npm/_cacache/tmp/git-clone*`, a
+directory it then cleans, and `postinstall` dies with `Cannot find module` before it
+can run. Cloning first avoids npm's git handling entirely. Verified on npm 11.18.
+
 Every release is mirrored to **GitHub Packages**. Treat that as redundancy rather
 than a second front door: GitHub Packages requires authentication even for public
 packages, so installing from it costs you a token that npmjs does not ask for.

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.6",
+  "version": "0.1.8",
   "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",