@hermespilot/link 0.5.0 → 0.5.2
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.
- package/README.md +8 -2
- package/dist/{chunk-VIBGAYU2.js → chunk-DZMN5RIV.js} +2591 -2252
- package/dist/cli/index.js +1508 -41
- package/dist/http/app.d.ts +53 -1
- package/dist/http/app.js +1 -1
- package/package.json +1 -1
- package/scripts/postinstall.mjs +6 -0
package/README.md
CHANGED
|
@@ -15,13 +15,19 @@ npm install -g @hermespilot/link
|
|
|
15
15
|
|
|
16
16
|
The package installs the `hermeslink` command. It does not start the service automatically during installation.
|
|
17
17
|
|
|
18
|
-
If your shell cannot find `hermeslink` right after install, your npm global bin directory is probably not on `PATH
|
|
18
|
+
If your shell cannot find `hermeslink` right after install, your npm global bin directory is probably not on `PATH`, or npm was run from a different environment than your shell. You can run the install diagnostic without relying on `PATH`:
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
npx --yes @hermespilot/link doctor --install
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
On Unix-like systems, the most common temporary fix is:
|
|
19
25
|
|
|
20
26
|
```bash
|
|
21
27
|
export PATH="$(npm prefix -g)/bin:$PATH"
|
|
22
28
|
```
|
|
23
29
|
|
|
24
|
-
You can also invoke the installed binary directly with `$(npm prefix -g)/bin/hermeslink`.
|
|
30
|
+
You can also invoke the installed binary directly with `$(npm prefix -g)/bin/hermeslink`. In WSL, if `npm prefix -g` points under `/mnt/c/...`, you are probably using Windows Node/npm from inside WSL. Install Linux Node.js inside WSL, or run both Hermes Agent and Hermes Link on the Windows host instead of mixing the two environments.
|
|
25
31
|
|
|
26
32
|
## Common commands
|
|
27
33
|
|