@vib795/agent-memory 0.1.6 → 0.1.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/HOWTO.md +5 -2
  2. package/README.md +9 -2
  3. package/package.json +1 -1
package/HOWTO.md CHANGED
@@ -70,11 +70,14 @@ agent-memory setup
70
70
  you have. Modern npm refuses to let a package run its own setup automatically — a
71
71
  sensible security default — so the second line is you giving permission, by hand.
72
72
 
73
- > No access to the npm registry at work? This works too, and needs nothing but GitHub:
73
+ > No access to the npm registry at work? Clone it instead. This needs nothing but
74
+ > GitHub, and it is what to use if your company proxy blocks or quarantines npm:
74
75
  > ```bash
75
- > npm install -g https://github.com/vib795/agent-memory.git
76
+ > git clone https://github.com/vib795/agent-memory.git
77
+ > npm install -g ./agent-memory
76
78
  > agent-memory setup
77
79
  > ```
80
+ > Clone first — installing from the git URL directly does not work. See the README.
78
81
 
79
82
  ### What just happened
80
83
 
package/README.md CHANGED
@@ -182,13 +182,20 @@ npm install -g @vib795/agent-memory
182
182
  agent-memory setup
183
183
  ```
184
184
 
185
- Straight from git works too, and needs no registry access:
185
+ No registry access? Clone it and install the directory. This needs nothing but
186
+ GitHub, and it is the path to use behind a proxy that blocks or quarantines npm:
186
187
 
187
188
  ```bash
188
- npm install -g https://github.com/vib795/agent-memory.git
189
+ git clone https://github.com/vib795/agent-memory.git
190
+ npm install -g ./agent-memory
189
191
  agent-memory setup
190
192
  ```
191
193
 
194
+ **Do not install from the git URL directly.** `npm install -g <git-url>` fails for
195
+ this package: npm links the package into `~/.npm/_cacache/tmp/git-clone*`, a
196
+ directory it then cleans, and `postinstall` dies with `Cannot find module` before it
197
+ can run. Cloning first avoids npm's git handling entirely. Verified on npm 11.18.
198
+
192
199
  Every release is mirrored to **GitHub Packages**. Treat that as redundancy rather
193
200
  than a second front door: GitHub Packages requires authentication even for public
194
201
  packages, so installing from it costs you a token that npmjs does not ask for.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vib795/agent-memory",
3
- "version": "0.1.6",
3
+ "version": "0.1.7",
4
4
  "description": "Durable cross-repo knowledge graph for GitHub Copilot and Claude Code. Markdown source of truth, disposable SQLite index, zero runtime dependencies.",
5
5
  "keywords": [
6
6
  "github-copilot",