@hydranium/data-client-vscode 1.0.0-next.395 → 1.0.0-next.396

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 (2) hide show
  1. package/README.md +1 -1
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -28,7 +28,7 @@ npm install @hydranium/data-client-vscode
28
28
  | Peer | Range |
29
29
  | -------------------------- | ------------- |
30
30
  | `@hydranium/protocol` | `^1.0.0-next` |
31
- | `vscode-jsonrpc` | `^9.0.0` |
31
+ | `vscode-jsonrpc` | `^9.0.3` |
32
32
  | `vscode-messenger` | `^0.4.5` |
33
33
  | `vscode-messenger-common` | `^0.4.5` |
34
34
  | `vscode-messenger-webview` | `^0.4.5` |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hydranium/data-client-vscode",
3
- "version": "1.0.0-next.395",
3
+ "version": "1.0.0-next.396",
4
4
  "description": "VS Code client primitives for the hydranium data-server protocol head; companion of @hydranium/data-server. The extension host relays the data-server's socket to a webview over a vscode-messenger hop, and the webview's data port reads it, so DataConnection and DataSession run unchanged in a webview.",
5
5
  "keywords": [
6
6
  "hydranium",
@@ -63,19 +63,19 @@
63
63
  "watch": "tsc -b -w --preserveWatchOutput"
64
64
  },
65
65
  "devDependencies": {
66
- "@hydranium/protocol": "1.0.0-next.395",
66
+ "@hydranium/protocol": "1.0.0-next.396",
67
67
  "@types/node": "^22.0.0",
68
68
  "@types/vscode": "^1.101.0",
69
69
  "rimraf": "^5.0.0",
70
70
  "typescript": "^7.0.2",
71
- "vscode-jsonrpc": "9.0.0",
71
+ "vscode-jsonrpc": "9.0.3",
72
72
  "vscode-messenger": "^0.4.5",
73
73
  "vscode-messenger-common": "^0.4.5",
74
74
  "vscode-messenger-webview": "^0.4.5"
75
75
  },
76
76
  "peerDependencies": {
77
- "@hydranium/protocol": "1.0.0-next.395",
78
- "vscode-jsonrpc": "^9.0.0",
77
+ "@hydranium/protocol": "1.0.0-next.396",
78
+ "vscode-jsonrpc": "^9.0.3",
79
79
  "vscode-messenger": "^0.4.5",
80
80
  "vscode-messenger-common": "^0.4.5",
81
81
  "vscode-messenger-webview": "^0.4.5"
@@ -95,7 +95,7 @@
95
95
  "node": ">=22.13",
96
96
  "vscode": "^1.101.0"
97
97
  },
98
- "//peerDependencies": "`vscode-jsonrpc` takes a caret, so the framework shares the transport the LSP connection resolves, which an `init` scaffold pins: each `vscode-languageserver-protocol` release pins its transport exactly, so an exact peer would name a copy a fresh install rarely holds. The caret excludes 8.x, so a tree whose top holds GLSP's copy fails the peer with a named ERESOLVE warning, an error under `--strict-peer-deps`, rather than resolving silently. No peer reaches a NESTED copy, such as GLSP's or one the LSP packages nest. The wire compares message types and `ResponseError`s by copy identity, so the framework sends typed messages by method name and recognises errors with `isResponseError` rather than `instanceof`.",
98
+ "//peerDependencies": "`vscode-jsonrpc` takes a caret, so the framework shares the transport the LSP connection resolves, which an `init` scaffold pins: each `vscode-languageserver-protocol` release pins its transport exactly, so an exact peer would name a copy a fresh install rarely holds. The caret starts at 9.0.3, the transport protocol 3.18.4 pins, since an earlier one leaves an unhandled rejection for a request written to a destroyed stream, and no protocol this framework accepts pins it. The caret excludes 8.x, so a tree whose top holds GLSP's copy fails the peer with a named ERESOLVE warning, an error under `--strict-peer-deps`, rather than resolving silently. No peer reaches a NESTED copy, such as GLSP's or one the LSP packages nest. The wire compares message types and `ResponseError`s by copy identity, so the framework sends typed messages by method name and recognises errors with `isResponseError` rather than `instanceof`.",
99
99
  "//prepack": "The publish guard, a `prepack` rather than a `prepare`: `prepack` runs only when a tarball is made (`npm pack`, `npm publish`) and never on install, so it cannot break the install it has no business touching. What it defends against: `files` lists `lib`, `lib` is gitignored, and a `files` entry matching nothing is skipped SILENTLY — so `npm publish` from an unbuilt tree emits a tarball of `src` and nothing else, with no error.",
100
100
  "//vscode-messenger": "The `vscode-messenger` packages are optional peers: the channel restates the two messenger shapes structurally, so the runtime tiers never pin the copy GLSP's VS Code integration brings, and only `./testing`, which joins the real classes, loads them."
101
101
  }