@hydranium/data-server 1.0.0-next.62 → 1.0.0-next.66
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/lib/data-server.d.ts +3 -3
- package/package.json +7 -7
- package/src/data-server.ts +3 -3
package/lib/data-server.d.ts
CHANGED
|
@@ -151,9 +151,9 @@ export interface DataServerOptions extends LogNameOptions {
|
|
|
151
151
|
* When supplied, every inbound data-server RPC is timed into this collector
|
|
152
152
|
* (via the `createRpcProxy` binding) and exposed through
|
|
153
153
|
* {@link DataServerDiagnosticsProtocol.getLatency}. A head that also runs an
|
|
154
|
-
* LSP connection can pass the SAME collector to
|
|
155
|
-
*
|
|
156
|
-
*
|
|
154
|
+
* LSP connection can pass the SAME collector through `lspLatencyOptions` to
|
|
155
|
+
* that connection, so one report covers both heads. Absent by default (no
|
|
156
|
+
* timing overhead).
|
|
157
157
|
*/
|
|
158
158
|
readonly latency?: LatencyCollector;
|
|
159
159
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@hydranium/data-server",
|
|
3
|
-
"version": "1.0.0-next.
|
|
3
|
+
"version": "1.0.0-next.66",
|
|
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
|
"hydranium",
|
|
@@ -75,18 +75,18 @@
|
|
|
75
75
|
"watch": "tsc -b -w --preserveWatchOutput"
|
|
76
76
|
},
|
|
77
77
|
"devDependencies": {
|
|
78
|
-
"@hydranium/core": "1.0.0-next.
|
|
79
|
-
"@hydranium/langium": "1.0.0-next.
|
|
80
|
-
"@hydranium/protocol": "1.0.0-next.
|
|
78
|
+
"@hydranium/core": "1.0.0-next.66",
|
|
79
|
+
"@hydranium/langium": "1.0.0-next.66",
|
|
80
|
+
"@hydranium/protocol": "1.0.0-next.66",
|
|
81
81
|
"rimraf": "^5.0.0",
|
|
82
82
|
"typescript": "^5.8.0",
|
|
83
83
|
"vscode-jsonrpc": "9.0.1",
|
|
84
84
|
"vscode-languageserver-textdocument": "^1.0.12"
|
|
85
85
|
},
|
|
86
86
|
"peerDependencies": {
|
|
87
|
-
"@hydranium/core": "1.0.0-next.
|
|
88
|
-
"@hydranium/langium": "1.0.0-next.
|
|
89
|
-
"@hydranium/protocol": "1.0.0-next.
|
|
87
|
+
"@hydranium/core": "1.0.0-next.66",
|
|
88
|
+
"@hydranium/langium": "1.0.0-next.66",
|
|
89
|
+
"@hydranium/protocol": "1.0.0-next.66",
|
|
90
90
|
"vscode-jsonrpc": "9.0.1",
|
|
91
91
|
"vscode-languageserver-textdocument": "^1.0.12"
|
|
92
92
|
},
|
package/src/data-server.ts
CHANGED
|
@@ -283,9 +283,9 @@ export interface DataServerOptions extends LogNameOptions {
|
|
|
283
283
|
* When supplied, every inbound data-server RPC is timed into this collector
|
|
284
284
|
* (via the `createRpcProxy` binding) and exposed through
|
|
285
285
|
* {@link DataServerDiagnosticsProtocol.getLatency}. A head that also runs an
|
|
286
|
-
* LSP connection can pass the SAME collector to
|
|
287
|
-
*
|
|
288
|
-
*
|
|
286
|
+
* LSP connection can pass the SAME collector through `lspLatencyOptions` to
|
|
287
|
+
* that connection, so one report covers both heads. Absent by default (no
|
|
288
|
+
* timing overhead).
|
|
289
289
|
*/
|
|
290
290
|
readonly latency?: LatencyCollector;
|
|
291
291
|
}
|