@hydranium/glsp-client-theia 1.0.0-next.176 → 1.0.0-next.177
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/package.json +24 -24
package/package.json
CHANGED
|
@@ -1,32 +1,40 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@hydranium/glsp-client-theia",
|
|
3
|
-
"version": "1.0.0-next.
|
|
3
|
+
"version": "1.0.0-next.177",
|
|
4
4
|
"description": "Theia-coupled client primitives for GLSP heads built on @hydranium/glsp-server. Provides the action dispatcher, channel logger, and connection-handler bases that Theia-based adopters extend; companion of @hydranium/glsp-server.",
|
|
5
5
|
"keywords": [
|
|
6
|
+
"diagram",
|
|
7
|
+
"glsp",
|
|
6
8
|
"hydranium",
|
|
7
9
|
"langium",
|
|
8
10
|
"language-server",
|
|
9
11
|
"lsp",
|
|
10
|
-
"glsp",
|
|
11
|
-
"diagram",
|
|
12
12
|
"theia"
|
|
13
13
|
],
|
|
14
14
|
"homepage": "https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/glsp-client-theia",
|
|
15
15
|
"bugs": {
|
|
16
16
|
"url": "https://github.com/eclipse-emfcloud/hydranium/issues"
|
|
17
17
|
},
|
|
18
|
+
"license": "MIT",
|
|
19
|
+
"author": {
|
|
20
|
+
"name": "Hydranium Team"
|
|
21
|
+
},
|
|
18
22
|
"repository": {
|
|
19
23
|
"type": "git",
|
|
20
24
|
"url": "https://github.com/eclipse-emfcloud/hydranium.git",
|
|
21
25
|
"directory": "packages/glsp-client-theia"
|
|
22
26
|
},
|
|
23
|
-
"
|
|
24
|
-
|
|
25
|
-
"
|
|
26
|
-
|
|
27
|
+
"files": [
|
|
28
|
+
"lib",
|
|
29
|
+
"src",
|
|
30
|
+
"style",
|
|
31
|
+
"!lib/**/*.tsbuildinfo"
|
|
32
|
+
],
|
|
27
33
|
"sideEffects": [
|
|
28
34
|
"**/*.css"
|
|
29
35
|
],
|
|
36
|
+
"main": "lib/index.js",
|
|
37
|
+
"types": "lib/index.d.ts",
|
|
30
38
|
"exports": {
|
|
31
39
|
".": {
|
|
32
40
|
"types": "./lib/index.d.ts",
|
|
@@ -58,14 +66,9 @@
|
|
|
58
66
|
},
|
|
59
67
|
"./style/diagram-loading.css": "./style/diagram-loading.css"
|
|
60
68
|
},
|
|
61
|
-
"
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
"lib",
|
|
65
|
-
"src",
|
|
66
|
-
"style",
|
|
67
|
-
"!lib/**/*.tsbuildinfo"
|
|
68
|
-
],
|
|
69
|
+
"publishConfig": {
|
|
70
|
+
"access": "public"
|
|
71
|
+
},
|
|
69
72
|
"scripts": {
|
|
70
73
|
"build": "tsc -b",
|
|
71
74
|
"clean": "rimraf lib tsconfig.tsbuildinfo",
|
|
@@ -79,10 +82,10 @@
|
|
|
79
82
|
"@eclipse-glsp/client": "2.7.0",
|
|
80
83
|
"@eclipse-glsp/server": "2.7.0",
|
|
81
84
|
"@eclipse-glsp/theia-integration": "2.7.0",
|
|
82
|
-
"@hydranium/client-theia": "1.0.0-next.
|
|
83
|
-
"@hydranium/core": "1.0.0-next.
|
|
84
|
-
"@hydranium/glsp-server": "1.0.0-next.
|
|
85
|
-
"@hydranium/protocol": "1.0.0-next.
|
|
85
|
+
"@hydranium/client-theia": "1.0.0-next.177",
|
|
86
|
+
"@hydranium/core": "1.0.0-next.177",
|
|
87
|
+
"@hydranium/glsp-server": "1.0.0-next.177",
|
|
88
|
+
"@hydranium/protocol": "1.0.0-next.177",
|
|
86
89
|
"@theia/core": "^1.70.0",
|
|
87
90
|
"@theia/process": "^1.70.0",
|
|
88
91
|
"@theia/workspace": "^1.70.0",
|
|
@@ -96,8 +99,8 @@
|
|
|
96
99
|
"peerDependencies": {
|
|
97
100
|
"@eclipse-glsp/client": "^2.6.0",
|
|
98
101
|
"@eclipse-glsp/theia-integration": "^2.6.0",
|
|
99
|
-
"@hydranium/client-theia": "1.0.0-next.
|
|
100
|
-
"@hydranium/protocol": "1.0.0-next.
|
|
102
|
+
"@hydranium/client-theia": "1.0.0-next.177",
|
|
103
|
+
"@hydranium/protocol": "1.0.0-next.177",
|
|
101
104
|
"@theia/core": "^1.70.0",
|
|
102
105
|
"@theia/process": "^1.70.0",
|
|
103
106
|
"@theia/workspace": "^1.70.0",
|
|
@@ -107,9 +110,6 @@
|
|
|
107
110
|
"engines": {
|
|
108
111
|
"node": ">=22.13"
|
|
109
112
|
},
|
|
110
|
-
"publishConfig": {
|
|
111
|
-
"access": "public"
|
|
112
|
-
},
|
|
113
113
|
"//exports": "The stylesheet key is an ASSET entry, not a module subpath, and it is spelled as the exact filename rather than `./style/*` so nothing becomes reachable automatically — the same no-wildcard property every other key here has. It exists because the widget's own import is package-RELATIVE, which `exports` does not gate, so the map's silence broke nobody inside the package while blocking every adopter who wants to `@import` the sheet, re-bundle it or override it by specifier; that failure reads as \"not exported under the conditions\" rather than as a missing entry. It has NO `./lib/style/...` twin, and must not grow one: the twin rule exists so a bare subpath is reachable from a node10 MODULE resolver, `tsc` emits no assets so there is no `lib/style/` to point at, and a bundler — which is what resolves a stylesheet — reads the map. `check:exports` carves out exactly this shape and asserts instead that the target file exists and is covered by `files`, which is the pair of mistakes an asset key can actually make.",
|
|
114
114
|
"//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.",
|
|
115
115
|
"//sideEffects": "A stylesheet IS the side effect: `style/diagram-loading.css` is pulled in by a bare import in `browser/diagram-widget.js`, and a CSS module exports nothing, so under a blanket `false` a bundler drops the import as unused and the diagram loading overlay renders unstyled. Nothing fails at build time. The glob rather than the importing module, so a second stylesheet is covered without another edit; the widget itself is reached through its exported class and needs no flag."
|