@hydranium/data-server 1.0.0-next.228 → 1.0.0-next.229

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 (1) hide show
  1. package/package.json +8 -8
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hydranium/data-server",
3
- "version": "1.0.0-next.228",
3
+ "version": "1.0.0-next.229",
4
4
  "description": "Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.",
5
5
  "keywords": [
6
6
  "data-server",
@@ -66,18 +66,18 @@
66
66
  "watch": "tsc -b -w --preserveWatchOutput"
67
67
  },
68
68
  "devDependencies": {
69
- "@hydranium/core": "1.0.0-next.228",
70
- "@hydranium/langium": "1.0.0-next.228",
71
- "@hydranium/protocol": "1.0.0-next.228",
69
+ "@hydranium/core": "1.0.0-next.229",
70
+ "@hydranium/langium": "1.0.0-next.229",
71
+ "@hydranium/protocol": "1.0.0-next.229",
72
72
  "rimraf": "^5.0.0",
73
73
  "typescript": "^7.0.2",
74
74
  "vscode-jsonrpc": "9.0.0",
75
75
  "vscode-languageserver-textdocument": "^1.0.12"
76
76
  },
77
77
  "peerDependencies": {
78
- "@hydranium/core": "1.0.0-next.228",
79
- "@hydranium/langium": "1.0.0-next.228",
80
- "@hydranium/protocol": "1.0.0-next.228",
78
+ "@hydranium/core": "1.0.0-next.229",
79
+ "@hydranium/langium": "1.0.0-next.229",
80
+ "@hydranium/protocol": "1.0.0-next.229",
81
81
  "vscode-jsonrpc": "^9.0.0",
82
82
  "vscode-languageserver-textdocument": "^1.0.12"
83
83
  },
@@ -85,6 +85,6 @@
85
85
  "node": ">=22.13"
86
86
  },
87
87
  "//browser": "Selects the diagnostics default per platform, the same mechanism @eclipse-glsp/server uses to swap its node build for its browser one. The Node module imports @hydranium/core/node; a browser bundler resolves the twin instead and therefore never follows that import, which is what keeps this package's `.` entry bundleable. Node ignores this field, so a Node host keeps the real implementation with no configuration. `check:neutral` is the proof it still applies — it bundles `.` for the browser and would fail on node:fs the moment the mapping stops matching.",
88
- "//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; docs/adopting/requirements.md has the chain. 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`.",
88
+ "//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`.",
89
89
  "//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."
90
90
  }