pi-link 0.1.15-beta.1 → 0.1.15
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/CHANGELOG.md +23 -18
- package/README.md +24 -1
- package/package.json +1 -6
package/CHANGELOG.md
CHANGED
|
@@ -6,17 +6,25 @@ This changelog is based on the git history from `2026-03-21` (initial commit) th
|
|
|
6
6
|
|
|
7
7
|
---
|
|
8
8
|
|
|
9
|
-
## 0.1.15
|
|
9
|
+
## 0.1.15 — 2026-05-18
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
Stable release for the 0.1.15 cycle, promoted after beta soak.
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
### Install note for Pi 0.75+
|
|
14
|
+
|
|
15
|
+
Pi 0.75 installs Pi packages under `~/.pi/agent/npm/`, so `pi install npm:pi-link` still enables the in-Pi extension features (`/link*`, tools, `--link`) but no longer puts the `pi-link` shell launcher on PATH.
|
|
16
|
+
|
|
17
|
+
If you use `pi-link <name>` from your shell, also install the launcher globally:
|
|
18
|
+
|
|
19
|
+
```sh
|
|
20
|
+
npm i -g pi-link
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
Users who only use pi-link inside Pi do not need this extra step. Background: [pi-mono#4587](https://github.com/earendil-works/pi-mono/issues/4587).
|
|
14
24
|
|
|
15
25
|
### Breaking
|
|
16
26
|
|
|
17
|
-
- **Pi 0.74+ is now required.**
|
|
18
|
-
- `index.ts`: imports `@earendil-works/pi-coding-agent` and `@earendil-works/pi-tui`
|
|
19
|
-
- `package.json` peer deps: `@earendil-works/pi-coding-agent` and `@earendil-works/pi-tui` at `>=0.74.0`
|
|
27
|
+
- **Pi 0.74+ is now required.** pi-link now uses the `@earendil-works/*` Pi package namespace. Users on Pi ≤0.73 should pin `pi-link@0.1.14`.
|
|
20
28
|
|
|
21
29
|
### Added
|
|
22
30
|
|
|
@@ -28,22 +36,23 @@ _Supersedes `0.1.15-beta.0`, which was pulled within hours due to a peer-dep nam
|
|
|
28
36
|
pi-link --resolve=<name>
|
|
29
37
|
```
|
|
30
38
|
|
|
31
|
-
- **Pi-bundled imports declared as peer dependencies** (using the new `@earendil-works/*` namespace, satisfied natively by Pi 0.74+). Previously only `ws` was declared, so consumers whose toolchain didn't auto-resolve modules through Pi's loader (e.g. some Docker setups) hit `ERR_MODULE_NOT_FOUND` on `typebox`. With modern npm/pnpm, peer deps auto-install when not provided by a parent.
|
|
32
|
-
|
|
33
39
|
### Changed
|
|
34
40
|
|
|
41
|
+
- **Removed Pi peer dependencies from `package.json`.** Pi provides its own extension APIs at load time; declaring them as npm peers caused unnecessary install warnings and duplicate package installs. `ws` remains the only runtime dependency.
|
|
35
42
|
- **`pi-link --resolve <missing-name>` now exits with code `2`** (was `0`). Single match still exits `0`; ambiguous still exits `1`; not found is now distinguishable from success in scripts. The legacy `pi-link resolve <missing-name>` form gets the same fix.
|
|
36
43
|
- **`pi-link <name> <extra-positional>` now errors** instead of silently passing the extra to Pi as a prompt. Catches typos like `pi-link resolv foo`. Tokens that follow a flag without `=` are still accepted as that flag's value (e.g. `pi-link worker --model opus` works). Use `--` to pass bare positionals through unchanged: `pi-link worker -- some-arg`.
|
|
37
44
|
- **`pi-link foo --help` now errors** with "cannot combine session name and --help" instead of silently passing `--help` to Pi. Run `pi --help` for Pi's own help.
|
|
38
|
-
- **Published tarball trimmed to 7 files
|
|
45
|
+
- **Published tarball trimmed to 7 files.** Explicit `files` allowlist so internal planning artifacts and the test harness no longer ship to npm.
|
|
39
46
|
|
|
40
47
|
### Deprecated
|
|
41
48
|
|
|
42
|
-
- **`pi-link list` and `pi-link resolve` subcommands.** Use `--list` / `--resolve` instead. Subcommands still work for one release with a stderr deprecation warning, then will be removed.
|
|
49
|
+
- **`pi-link list` and `pi-link resolve` subcommands.** Use `--list` / `--resolve` instead. Subcommands still work for one release with a stderr deprecation warning, then will be removed.
|
|
43
50
|
|
|
44
51
|
### Migration from 0.1.14
|
|
45
52
|
|
|
46
|
-
|
|
53
|
+
Existing launcher aliases keep working for this release, but deprecated `list` / `resolve` subcommands now print a stderr warning.
|
|
54
|
+
|
|
55
|
+
One behavior change may affect scripts: `pi-link resolve <missing>` now exits `2` instead of `0`, so callers that trusted exit `0` to mean "found" should update their handling.
|
|
47
56
|
|
|
48
57
|
To silence the deprecation warning, switch to the flag form:
|
|
49
58
|
|
|
@@ -55,19 +64,15 @@ To silence the deprecation warning, switch to the flag form:
|
|
|
55
64
|
| `pi-link resolve foo -g` | `pi-link --resolve foo -g` |
|
|
56
65
|
| `pi-link resolve --global foo` | `pi-link --resolve foo --global` (order matters in canonical form) |
|
|
57
66
|
|
|
58
|
-
### Test coverage
|
|
59
|
-
|
|
60
|
-
40 automated cases in `test/cli-flags-test.mjs` covering: canonical forms (5), deprecation aliases (4), orphan-positional rejection (7), mode-selecting validation (11), help / unknown / managed-flag rejection (8), wrapper-vs-pi flag boundaries (4). Cases that exercise the launch path use a stubbed `pi` on PATH that records argv + `PI_LINK_NAME`. Run with `node test/cli-flags-test.mjs`.
|
|
61
|
-
|
|
62
67
|
---
|
|
63
68
|
|
|
64
69
|
## 0.1.15-beta.0 — 2026-05-17 _(pulled — do not install)_
|
|
65
70
|
|
|
66
|
-
Initial 0.1.15 beta
|
|
71
|
+
Initial 0.1.15 beta, superseded by `0.1.15`.
|
|
67
72
|
|
|
68
|
-
**Issue:** peer dependencies still pointed at the old `@mariozechner/*` namespace,
|
|
73
|
+
**Issue:** peer dependencies still pointed at the old `@mariozechner/*` namespace, causing npm to install deprecated Pi 0.73 packages on Pi 0.74+ systems.
|
|
69
74
|
|
|
70
|
-
**Resolution:**
|
|
75
|
+
**Resolution:** stable `0.1.15` uses the `@earendil-works/*` runtime imports and removes Pi npm peer dependencies.
|
|
71
76
|
|
|
72
77
|
---
|
|
73
78
|
|
package/README.md
CHANGED
|
@@ -45,14 +45,37 @@ A single Pi terminal is powerful. Multiple terminals working together unlock new
|
|
|
45
45
|
|
|
46
46
|
### Install
|
|
47
47
|
|
|
48
|
+
The minimum install — enables every in-Pi feature (`/link`, `link_send`, `link_prompt`, `/link-connect`, `--link` flag, auto-resume, all LLM tools):
|
|
49
|
+
|
|
48
50
|
```bash
|
|
49
51
|
pi install npm:pi-link
|
|
50
52
|
```
|
|
51
53
|
|
|
54
|
+
That's it. For most users this is all you need.
|
|
55
|
+
|
|
56
|
+
#### Optional: shell launcher
|
|
57
|
+
|
|
58
|
+
If you also want the `pi-link <name>` shell command to start named sessions from a terminal prompt (e.g. `pi-link builder` in one window, `pi-link reviewer` in another), install the CLI globally as well:
|
|
59
|
+
|
|
60
|
+
```bash
|
|
61
|
+
npm i -g pi-link
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
Or install both in one line:
|
|
65
|
+
|
|
66
|
+
```bash
|
|
67
|
+
pi install npm:pi-link && npm i -g pi-link
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
The shell launcher is convenience-only — you can always reach the same functionality from inside Pi via `/link-connect <name>` and `/link-name <name>`.
|
|
71
|
+
|
|
72
|
+
> **Why two installs?** Pi 0.75 installs Pi packages into a private npm root (`~/.pi/agent/npm/`) for safer permission handling ([pi-mono#4587](https://github.com/earendil-works/pi-mono/issues/4587)). That's where the Pi extension lives, but it means the `pi-link` shell command is no longer on system PATH. `npm i -g pi-link` puts it on PATH separately. Both installs are safe to use together.
|
|
73
|
+
|
|
52
74
|
### Uninstall
|
|
53
75
|
|
|
54
76
|
```bash
|
|
55
|
-
pi uninstall npm:pi-link
|
|
77
|
+
pi uninstall npm:pi-link # Remove Pi extension
|
|
78
|
+
npm uninstall -g pi-link # Remove CLI launcher (if you installed it)
|
|
56
79
|
```
|
|
57
80
|
|
|
58
81
|
### Usage
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-link",
|
|
3
|
-
"version": "0.1.15
|
|
3
|
+
"version": "0.1.15",
|
|
4
4
|
"description": "WebSocket-based inter-terminal communication for Pi. Connect multiple Pi terminals over a local link network.",
|
|
5
5
|
"author": "alvivar",
|
|
6
6
|
"license": "MIT",
|
|
@@ -30,11 +30,6 @@
|
|
|
30
30
|
"dependencies": {
|
|
31
31
|
"ws": "^8.20.0"
|
|
32
32
|
},
|
|
33
|
-
"peerDependencies": {
|
|
34
|
-
"@earendil-works/pi-coding-agent": ">=0.74.0",
|
|
35
|
-
"@earendil-works/pi-tui": ">=0.74.0",
|
|
36
|
-
"typebox": "*"
|
|
37
|
-
},
|
|
38
33
|
"devDependencies": {
|
|
39
34
|
"@types/ws": "^8.18.1"
|
|
40
35
|
},
|