@hydranium/client-theia 1.0.0-next.210 → 1.0.0-next.213

package/README.md

@@ -93,7 +93,7 @@ declared peer dependencies are:
 | `@theia/filesystem`   | `^1.70.0`     |
 | `@theia/output`       | `^1.70.0`     |
 | `inversify`           | `^6.0.0`      |
-| `vscode-jsonrpc`      | `9.0.1`       |
+| `vscode-jsonrpc`      | `^9.0.0`      |
 
 `@theia/output` is easy to miss: the memory-diagnostics commands and the channel
 logger both write to an Output channel, so a host that does not already depend on

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hydranium/client-theia",
-  "version": "1.0.0-next.210",
+  "version": "1.0.0-next.213",
   "description": "Cross-head Theia client primitives shared by the hydranium protocol heads. Provides the socket-forwarding connection-handler base that the data-server and GLSP Theia integrations subclass, plus the preference-driven Output-channel logger; carries no head-specific dependency.",
   "keywords": [
     "hydranium",
@@ -81,7 +81,7 @@
     "watch": "tsc -b -w --preserveWatchOutput"
   },
   "devDependencies": {
-    "@hydranium/protocol": "1.0.0-next.210",
+    "@hydranium/protocol": "1.0.0-next.213",
     "@theia/core": "^1.70.0",
     "@theia/editor": "^1.70.0",
     "@theia/filesystem": "^1.70.0",
@@ -91,20 +91,20 @@
     "reflect-metadata": "0.2.2",
     "rimraf": "^5.0.0",
     "typescript": "^7.0.2",
-    "vscode-jsonrpc": "9.0.1"
+    "vscode-jsonrpc": "9.0.0"
   },
   "peerDependencies": {
-    "@hydranium/protocol": "1.0.0-next.210",
+    "@hydranium/protocol": "1.0.0-next.213",
     "@theia/core": "^1.70.0",
     "@theia/editor": "^1.70.0",
     "@theia/filesystem": "^1.70.0",
     "@theia/output": "^1.70.0",
     "inversify": "^6.0.0",
-    "vscode-jsonrpc": "9.0.1"
+    "vscode-jsonrpc": "^9.0.0"
   },
   "engines": {
     "node": ">=22.13"
   },
-  "//peerDependencies": "@theia/core stays at 1.70 here, matching the sibling Theia packages, even though the connection-resilience bindings need 1.71: Theia only began binding `SocketWriteBuffer` then, and before that each connection built one privately, so there is no binding to rebind. Rather than split the package's floor for one feature, `bindConnectionResilience` probes for that binding and warns instead of installing when it is absent — a capability check rather than a version parse, so it answers about the container in front of it. Everything else the feature touches exists at 1.70, and the emitted declarations deliberately name no type that 1.70 lacks, so the package still compiles there. Verified by unpacking 1.70, 1.71 and 1.72, not inferred from a changelog. `vscode-jsonrpc` is EXACT because it is one link of an atomic chain: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value is a second physical copy, and this wire stack breaks on copy identity.",
-  "//prepack": "The publish guard, and it deliberately is NOT a `prepare`: npm runs a workspace `prepare` BEFORE the root `postinstall` that applies patches/vscode-jsonrpc+9.0.1.patch, so building there fails on a cold clone and npm rolls the entire install back. `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. It FAILS rather than rebuilds, because the rebuild is exactly the part that ordering defeats. 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."
+  "//peerDependencies": "@theia/core stays at 1.70 here, matching the sibling Theia packages, even though the connection-resilience bindings need 1.71: Theia only began binding `SocketWriteBuffer` then, and before that each connection built one privately, so there is no binding to rebind. Rather than split the package's floor for one feature, `bindConnectionResilience` probes for that binding and warns instead of installing when it is absent — a capability check rather than a version parse, so it answers about the container in front of it. Everything else the feature touches exists at 1.70, and the emitted declarations deliberately name no type that 1.70 lacks, so the package still compiles there. Verified by unpacking 1.70, 1.71 and 1.72, not inferred from a changelog. `vscode-jsonrpc` takes a caret: each `vscode-languageserver-protocol` release pins its transport exactly, so an exact peer would name a copy a fresh install rarely holds, while the caret still excludes the 8.x line.",
+  "//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."
 }