{"_id":"@hydranium/data-server","_rev":"105-61ee584626df6272b9a5b1d072673c51","name":"@hydranium/data-server","dist-tags":{"latest":"1.0.0-next.185"},"versions":{"1.0.0-next.4":{"name":"@hydranium/data-server","version":"1.0.0-next.4","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.4","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"0fd4e41655c0f6a1fb705e39a02191d21c910879","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.4.tgz","fileCount":48,"integrity":"sha512-BPIHRhEPjSU2QtzL01iGYtGoPqSWA4S7fITlrS7mQ4WCFNkkLQVn2EvgXq8wJIttjS8dzK4CSO7/dDxsNu+3tA==","signatures":[{"sig":"MEQCIFIEnRPph5suydzGHq8h6XNpIuboFvvr5bVGFROGyAiCAiBxm60yz7XpZ+Zm6TLi/ZIZeDxNw70wwGtdP7gGkZyoIQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"unpackedSize":244958},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"1a9c19ae00d0cf51baf7e7c7265de5649dbd2201","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"mfleck","email":"mfleck@eclipsesource.com"},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"10.9.2","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.4","@hydranium/langium":"1.0.0-next.4","@hydranium/protocol":"1.0.0-next.4","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.4","@hydranium/langium":"1.0.0-next.4","@hydranium/protocol":"1.0.0-next.4","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.4_1788908672010_0.27918281372306275","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.5":{"name":"@hydranium/data-server","version":"1.0.0-next.5","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.5","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"b091a5d61b0372d217dab8d8ced834c152e791a5","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.5.tgz","fileCount":48,"integrity":"sha512-syUilaNngAD0SEqaEHfv3M8GJnpwkAMO8+b1fPG5zjWPV7cKMIeGYQ4b2Wd82R883uylE7IG/Vuzk3CKJyhFUA==","signatures":[{"sig":"MEUCIGg2zX3hwQJRznD9THGD3ykiMTb85/dz0ZT/JKTDCTUGAiEAgt+/7eZajUCCZHJiULq9BL6oPo6ekMomwQQ4GneN7uU=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.5","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244958},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"f5015cdb0f6c921eacbda8fb315f82ffcb02d809","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.5","@hydranium/langium":"1.0.0-next.5","@hydranium/protocol":"1.0.0-next.5","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.5","@hydranium/langium":"1.0.0-next.5","@hydranium/protocol":"1.0.0-next.5","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.5_1788911144842_0.18755929835647933","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.6":{"name":"@hydranium/data-server","version":"1.0.0-next.6","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.6","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"d6859c0027f40b41c809c7f976c863865827f690","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.6.tgz","fileCount":48,"integrity":"sha512-+fPAe+luRJYrDsePKU0dkaWSJ+c4CpI4FCqsoFcAnFdB458tn6swcuSA9PhbzV+bBxJWTlKLi1/69pHMdQUNsA==","signatures":[{"sig":"MEQCICyI6WSceI4aIZG5jjn1JD6ZNmAwjFjW3Sez9GqJLL85AiBDKTBM3+Syp3iA3s9UOP5CP9+ea9OIX0ohUj3skY08xA==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.6","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244958},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"ff6cf31235dd051e35a6fed0799cac3b71a26192","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.6","@hydranium/langium":"1.0.0-next.6","@hydranium/protocol":"1.0.0-next.6","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.6","@hydranium/langium":"1.0.0-next.6","@hydranium/protocol":"1.0.0-next.6","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.6_1788945399048_0.4581844185938442","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.7":{"name":"@hydranium/data-server","version":"1.0.0-next.7","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.7","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"6de9c436f822b05a1af3d0dfa4ae57deb21dedc7","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.7.tgz","fileCount":48,"integrity":"sha512-eZF/jIFzpzD5p1nsTOMZVlytE12zT/3rRLB6No29OQP4tzTHe99xEIP7KlrIw4TMTltPE2E6TFM1FqQVxBArJA==","signatures":[{"sig":"MEUCIC9HCYnaUfW7ylWOOmcpyTeM5ilTcL8KZrZbEUAIaMvNAiEA0J18mRER3zSWW14FYmAe7zdWqkEb+we8i3U155Tv9ng=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.7","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244958},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"d03f6f4fc7bb5b114df9eb43fe8a4fd260fa225e","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.7","@hydranium/langium":"1.0.0-next.7","@hydranium/protocol":"1.0.0-next.7","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.7","@hydranium/langium":"1.0.0-next.7","@hydranium/protocol":"1.0.0-next.7","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.7_1788953521618_0.655864362038052","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.8":{"name":"@hydranium/data-server","version":"1.0.0-next.8","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.8","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"c9328ef57cd6a23dfb797694ac1291594511a27f","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.8.tgz","fileCount":48,"integrity":"sha512-3ytW+S/A691anbB/SrPvcFC2LxBfr2U4qv65cGgWSHQd8jWSMQi4BVHAC/JVZbhu4uwa6EKmCubvAcXz+Y0dKw==","signatures":[{"sig":"MEUCIBqmHRxQD55kVnKGbf3TAWTK7jR69spgeJWh9nQHbACcAiEAzuInZJG9nHkn39Ee/JqMI9/DX3C2IuiuXxXd2fM127Q=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.8","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244958},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"9a14d2811974e7d8c0be2ae7694173eabe4c53cc","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.8","@hydranium/langium":"1.0.0-next.8","@hydranium/protocol":"1.0.0-next.8","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.8","@hydranium/langium":"1.0.0-next.8","@hydranium/protocol":"1.0.0-next.8","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.8_1788954011974_0.855289700015752","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.9":{"name":"@hydranium/data-server","version":"1.0.0-next.9","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.9","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"cdc5f6a8572aea55c007e38f7b11611f18f78a9e","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.9.tgz","fileCount":48,"integrity":"sha512-HoADsfBQN+NOPERyX/izN+T0kmkYeoLA428+DGANe01ZxuUiTtrw5CJJug/HHINe5BR1r8DLGdw4jVlcZvH0qQ==","signatures":[{"sig":"MEUCIQDRSvv2p8uv8KiqTJPRDyMk5UVoiduBJ3HWRWUWilX9ugIgLvWK6WeQ3n7Uj4U8Rm1sMbMgsPvkQTxTBlPMgNkLfug=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.9","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244958},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"5c4804b9a2b192c743997952bcd0c53efd740816","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.9","@hydranium/langium":"1.0.0-next.9","@hydranium/protocol":"1.0.0-next.9","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.9","@hydranium/langium":"1.0.0-next.9","@hydranium/protocol":"1.0.0-next.9","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.9_1788958092210_0.49270393233629317","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.10":{"name":"@hydranium/data-server","version":"1.0.0-next.10","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.10","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"b4744f5f42c666a89da7a77fe5746e6a9d7293d5","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.10.tgz","fileCount":48,"integrity":"sha512-ALsvwbSY7IbQ6epld4dGY9AWw4Un4t2wi6inEJsyG9r4Ml+3QA5Ny80dxyLs/n2Lx4pqKBPZls78GpuCXVpI9A==","signatures":[{"sig":"MEYCIQC8kuZKNHsUTsUFu4pS5cIxSQC08BTNQ+asIkvlzPOizgIhAMAd2hr/fMPA5saunz6wfAOCKdWy5kcTBdAQSzHC8HRE","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.10","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244965},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"df66e1a949244721ac48fd2ea072f7f2c89cf013","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.10","@hydranium/langium":"1.0.0-next.10","@hydranium/protocol":"1.0.0-next.10","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.10","@hydranium/langium":"1.0.0-next.10","@hydranium/protocol":"1.0.0-next.10","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.10_1788962827716_0.27589669742769374","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.11":{"name":"@hydranium/data-server","version":"1.0.0-next.11","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.11","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"6be2f4ea507280b23ba663f03683afa158db6e5e","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.11.tgz","fileCount":48,"integrity":"sha512-TvPsiGyB5l7LSNfANQzACd7VwcUdwi28eugSRK/lOYFBoGQyl9ZeZUZBXBFUjKJSRHe4B+IZAiLI6ITfzY3Kng==","signatures":[{"sig":"MEUCIQCFucYI72ZH/Loy6y4UXnMSNaBfzoqlc2NNPR0qN/idpwIgNRmlME6a5h+aCMosD/SuSDQvMxj36lEs9o2CpJdNHNI=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.11","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244965},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"a4732457347fc331a6f3bee38f8cb43051df499f","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.11","@hydranium/langium":"1.0.0-next.11","@hydranium/protocol":"1.0.0-next.11","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.11","@hydranium/langium":"1.0.0-next.11","@hydranium/protocol":"1.0.0-next.11","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.11_1788963495800_0.9519295603335245","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.12":{"name":"@hydranium/data-server","version":"1.0.0-next.12","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.12","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"b24f46487da1fbdfd20d80ea1726719b92edfc5b","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.12.tgz","fileCount":48,"integrity":"sha512-QhTkXjgnYAED1o/eK6e2kZUzno0jt9oxNVLlQx+7XC8zK8WfmhMieEdAgpK/dRQH1c1sMdhNoRpoTh4eDUCA3w==","signatures":[{"sig":"MEQCIEANP6DsCUFMlGWjW3RVKFEpMSGUVOMTAS68thgbGdWtAiAw5LVrpz5/T7ViqRTdxhYvWAZvPiUoecC9KTJ62CridQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.12","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244965},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"ab9568ab15443597620edc79187d92f0ea68354f","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.12","@hydranium/langium":"1.0.0-next.12","@hydranium/protocol":"1.0.0-next.12","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.12","@hydranium/langium":"1.0.0-next.12","@hydranium/protocol":"1.0.0-next.12","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.12_1788969567285_0.5452294317906901","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.13":{"name":"@hydranium/data-server","version":"1.0.0-next.13","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.13","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"9632a64d0e7915f5fc5359109121ac2438cfee37","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.13.tgz","fileCount":48,"integrity":"sha512-6emhiPSN0BRsLfVpNW1hKJcUl8agBu9FNzL6qeAay9TNM2EV8HpHrhNHqSBhf6t8ChJoV95ii3RL6h0pkyMuvw==","signatures":[{"sig":"MEUCIGHJizysGB1oHxH24rDwU4ZHXEjGtnqu13Tnd9eDadiLAiEAw2D9Ww5QDFIbHs/6a72qM2i98A721KukC7DGuABzx30=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.13","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244965},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"7f5d29a1ace1f03b0a3f0f7278182beb408048bb","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.13","@hydranium/langium":"1.0.0-next.13","@hydranium/protocol":"1.0.0-next.13","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.13","@hydranium/langium":"1.0.0-next.13","@hydranium/protocol":"1.0.0-next.13","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.13_1789027788105_0.4786808204596795","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.14":{"name":"@hydranium/data-server","version":"1.0.0-next.14","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.14","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"e6ecd632258d0dc90e143ac2a811f76b26b4c487","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.14.tgz","fileCount":48,"integrity":"sha512-IllXxQSHE+OnUjsHUH+QlZs3dwKiwRHrwHWqoVFvzLI9MWKyDIW/+p9cZTmJH7rn3etPUr0chmqthT/OOj+jsw==","signatures":[{"sig":"MEUCIQCgNilA7ycGlAKV6gKgc7l+8/AIcLB3QkGc81w0f73H5gIgVSUTJt9EMkgUMtHduu/U6MI9XtBt+xLDUnHU3C6m30o=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.14","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244965},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"ceb4d6188cc57a327ade5469af6a220bc5b5bf0c","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.14","@hydranium/langium":"1.0.0-next.14","@hydranium/protocol":"1.0.0-next.14","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.14","@hydranium/langium":"1.0.0-next.14","@hydranium/protocol":"1.0.0-next.14","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.14_1789032193507_0.6031311833826845","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.15":{"name":"@hydranium/data-server","version":"1.0.0-next.15","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.15","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"39f2e3039939b01e82c1a383aea047156eed29a2","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.15.tgz","fileCount":48,"integrity":"sha512-vj8keh35yeohzxt+ZHQ2VINs7EM3EeNaJ9SBgR1EIssGk8qG9bB0neK5vZrDyLKbkFEc4XZ1nbVIN0gdnVlivA==","signatures":[{"sig":"MEUCIQDaUD82bnn7H600/hHKA1cTlysL8hLpjUXjs+KO+wKf6AIgLClR/5guEv7onrZzseQT0qf5lNIZZxzmd9KJ3IKFYyw=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.15","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244965},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"65f465437d22972c3a50c6be1419e791a59140ac","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.15","@hydranium/langium":"1.0.0-next.15","@hydranium/protocol":"1.0.0-next.15","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.15","@hydranium/langium":"1.0.0-next.15","@hydranium/protocol":"1.0.0-next.15","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.15_1789032737503_0.25042615910672583","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.16":{"name":"@hydranium/data-server","version":"1.0.0-next.16","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.16","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"c2cbb317a3cc4e86e309221007c2a97f6b68df6b","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.16.tgz","fileCount":48,"integrity":"sha512-1yZ3E89JkcOopBrWg0QC4gjYW64HCT8PnpVva4AInwijcjtalihF6ZqJnFi9QfCS7nhIgx2+9FD1mo1g2fFREw==","signatures":[{"sig":"MEUCIQDB4Ri7/WX9tMA+cdAVCU8PWBpo9nKl8upkexDZjMXHuwIgDbHXXlYzq/ANaS+Yd/rKQI25fPJEcD/Gp+BnLpH3z0E=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.16","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244965},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"c1f791ba46d6e8c824a20b3f04a1ea065d97293d","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.16","@hydranium/langium":"1.0.0-next.16","@hydranium/protocol":"1.0.0-next.16","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.16","@hydranium/langium":"1.0.0-next.16","@hydranium/protocol":"1.0.0-next.16","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.16_1789033828468_0.20166598304663141","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.17":{"name":"@hydranium/data-server","version":"1.0.0-next.17","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.17","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"488776382fe26ba22df0bc36f70db889ce84fbb8","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.17.tgz","fileCount":48,"integrity":"sha512-AOXiyriiDdeI54ZzCx4Vx7zmFGD49nNte+2+U4ZoO8XlOPhlqiaT7VpvW4ODdwEj4DzroIw0taAo/WbNNQpbbw==","signatures":[{"sig":"MEUCIQC2DYx/vJrHliD8TeXFMZQ2z4l492FXUXpdx2jqoqYTiwIgKIYGvHPoLYNJcFRMaiMODUsIdXSiJJT/h6d6agO0XXI=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.17","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244965},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"6d4d2f2deccdbbc13eb11ff633a3887e6d977a72","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.17","@hydranium/langium":"1.0.0-next.17","@hydranium/protocol":"1.0.0-next.17","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.17","@hydranium/langium":"1.0.0-next.17","@hydranium/protocol":"1.0.0-next.17","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.17_1789037156712_0.3945303924770869","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.18":{"name":"@hydranium/data-server","version":"1.0.0-next.18","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.18","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"adba9050b8fa25c6529106e6c87b322159362d88","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.18.tgz","fileCount":48,"integrity":"sha512-RlwGnav4erbIyIZdCkf+7iHUnIARGRK0pNIwlawZfdXJLsr3ugfpFqyPGV8RZV8u1psoYh4GB/6RfgvjMUPyjw==","signatures":[{"sig":"MEYCIQCM8/FHslq/xYBhOqWLYkNJGEnAtgRG7nzTo1OkjNNB3QIhAIW906WP3Xm/ZpPU+hNplGy/gS9tK7YjtGBworh7eEBm","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.18","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244965},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"45f73468e05c55b570b298470deeac748abcdb4d","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.18","@hydranium/langium":"1.0.0-next.18","@hydranium/protocol":"1.0.0-next.18","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.18","@hydranium/langium":"1.0.0-next.18","@hydranium/protocol":"1.0.0-next.18","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.18_1789038261248_0.7178712108789906","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.19":{"name":"@hydranium/data-server","version":"1.0.0-next.19","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.19","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"70b8bc8da997c42846f36fb5c837f30cec7f1e22","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.19.tgz","fileCount":48,"integrity":"sha512-bKlhcbXkB2nIShB3tzJOOL7JKwIae3YH9plzfsNhFkRXdpvjirbOv/MPamNXaYOy5gaijw+FMWzkrvBwXXmgKQ==","signatures":[{"sig":"MEUCIQDmmD59PIAW0wnKTSnIWE8PFy9b5gaXOiQFfKWwkma7mwIgRBf/cPJ4ewpa5qVD6rHbDsQc+rmvWTlCGMdwU3HpGn0=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.19","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":244965},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"cfb68570ae14c4b434bd31a4c5f8f59d007c92c6","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.19","@hydranium/langium":"1.0.0-next.19","@hydranium/protocol":"1.0.0-next.19","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"^8.0.0 || ^9.0.0","@hydranium/core":"1.0.0-next.19","@hydranium/langium":"1.0.0-next.19","@hydranium/protocol":"1.0.0-next.19","vscode-languageserver-textdocument":"^1.0.12"},"_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.19_1789046978795_0.530911891521376","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.22":{"name":"@hydranium/data-server","version":"1.0.0-next.22","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.22","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"ea7bc36833dc6995d6d3b48f6b499b287fd4af90","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.22.tgz","fileCount":48,"integrity":"sha512-t6hUaUhICFrFd5zvlmusZxvV7RPWbM2mLvOXhRI1J7CPN3HJel19wpfottZfyzeMhq1uBzQKbD3oInF62hMFmw==","signatures":[{"sig":"MEYCIQCGvBJsZ2g4guIEGy34PpVhvnDiP2Khg9OFvAx2so0zWgIhAN+FBV4KbzEEhzURtGhcWvAmSuRmypBV2KSrt1QB3jTI","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCLM95mRtndOZkBrNWQeEPdi13ivVPfzyxhLySTG0bXxQIhALsarSFci/hba4dDkQCMohOFrp/LvRaIouDn9QdKAgLS","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.22","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":246183},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"4760e9872df915a5ff865eefe8d7d755bd652edd","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.22","@hydranium/langium":"1.0.0-next.22","@hydranium/protocol":"1.0.0-next.22","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.22","@hydranium/langium":"1.0.0-next.22","@hydranium/protocol":"1.0.0-next.22","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.22_1789072026711_0.8100068223037662","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.23":{"name":"@hydranium/data-server","version":"1.0.0-next.23","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.23","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"bb94680fcc68ef918766dbf316c459b26822016e","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.23.tgz","fileCount":48,"integrity":"sha512-b5dFSoL8QjStDV3WeW34E0uDQLofYT9iyFoUhwVCd8UIsZU+ZSq+foW+ieGjLZ81wyb7tKk5LECBe4q8MkYSwQ==","signatures":[{"sig":"MEUCIQCH9n8jAfkwWrGYGrtrcF/EmjPfDbi0abd3PNdc8bALKAIgM1rNXDtzVk4HEdAlrerU549yo7cQZnVCG5tj7D/RksQ=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQDJqJUzt4w4se3zhUCLU/dtQPAqbqZTAkB44rR2ZdHAdwIhAOL0ESdsY4VzPchLGVs0MMjZsTLJOyqaODqirPBet2+J","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.23","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":246183},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"68adb62594d9eb65eb8b75d0ebe326a48f75b56f","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.23","@hydranium/langium":"1.0.0-next.23","@hydranium/protocol":"1.0.0-next.23","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.23","@hydranium/langium":"1.0.0-next.23","@hydranium/protocol":"1.0.0-next.23","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.23_1789073239636_0.6685956288081283","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.24":{"name":"@hydranium/data-server","version":"1.0.0-next.24","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.24","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"a5418b507ec4f542b3139bf59402a83009483df5","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.24.tgz","fileCount":48,"integrity":"sha512-Wlf2Jon0+ZGb1ml533bLFMHW+JZszt5efeVEd0rJx+VFh28+LNHEFTF1JpaJbbabcC/Dp9rY11i7KSH8DcdoCA==","signatures":[{"sig":"MEUCIQCaLfE/Znau/gBeWsf6ULLPNrcRG3wWD6zS6tL4H8Rv0QIgXKvxCl1TjxSmQB0F3HpTq4PhnwruXsJbuiT2AfcMqYs=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIDiOquteXMamq48UITXba0ntoE/aUtm6SlnsaZNesum3AiANhSTnebw8fNkeSZ4p6uGrMg2XBqDRkned3kRFRGXCEQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.24","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":246183},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"f15d0358de98a5c446955533021308196bf98b9b","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.24","@hydranium/langium":"1.0.0-next.24","@hydranium/protocol":"1.0.0-next.24","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.24","@hydranium/langium":"1.0.0-next.24","@hydranium/protocol":"1.0.0-next.24","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.24_1789074097102_0.9804986621543244","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.25":{"name":"@hydranium/data-server","version":"1.0.0-next.25","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.25","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"bb3b41037e38a184188e8cf0b75a375444e5456f","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.25.tgz","fileCount":48,"integrity":"sha512-PqUNkg8ycrX/ar/Tb2ufrZjsSSZTJBC2fADxtcrf7jtzY1fzN3arC+WG1twf+2lxx0OwVWFVWTzjpGbtiSQs3A==","signatures":[{"sig":"MEUCIQCAJpjOz5HstqAAGkT+RtjZV9IK9iDdlKnKJ8/m+3z15AIgKmBou/4widpKK/Mhx+eb0Kz+SOKDcWPKM1Iv2GAFFkU=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIB6ogNWg07oFyS9xyBkBhtlQbSo/e0j3bMQQLOLGuB8tAiAX6JXh+AE9FdYcgG/fYyApDdcs+olY2Dtp6CCrz9EwyQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.25","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":246183},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"}},"gitHead":"b69d464b0c1b93346cd29f9ca4f1cf8f1e8cf289","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.25","@hydranium/langium":"1.0.0-next.25","@hydranium/protocol":"1.0.0-next.25","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.25","@hydranium/langium":"1.0.0-next.25","@hydranium/protocol":"1.0.0-next.25","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.25_1789075277457_0.2838489578267731","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.27":{"name":"@hydranium/data-server","version":"1.0.0-next.27","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.27","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"e788bbb77f4000b87abaf7fa9cb953a5eb1d7cb1","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.27.tgz","fileCount":53,"integrity":"sha512-DRN+HwDIiF1Uyr1W5gBT2+LS3on21kaGYkDeE5k9R71R9rio4ZTYwG4RwtRuV9G54YOvjvnttW8yGuajwp+Epg==","signatures":[{"sig":"MEUCIQCWoxqNJP0UjjnXOaAGISe5flkO1EJ9U7Gp8hXqowvnlAIgOnlUfQzoeuCL7Rnqad858F/t65l9Hdwy/zl1W/jxar4=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCX6nkFl3uMDLcwXll7pi12rG1kE3pcYOr1OaLye2NiaQIhANPLkmXt4nH1pbppiCNMHADiM/Yh81imd+h733xNxMGf","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.27","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":252420},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"f0ad5bdc8d848ff48a6c0fe2afa6f8400cd96f9f","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.27","@hydranium/langium":"1.0.0-next.27","@hydranium/protocol":"1.0.0-next.27","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.27","@hydranium/langium":"1.0.0-next.27","@hydranium/protocol":"1.0.0-next.27","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.27_1789076564281_0.5987486013856018","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.28":{"name":"@hydranium/data-server","version":"1.0.0-next.28","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.28","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"73e5b93fe5ba854580e59fd08077425bc83f28f8","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.28.tgz","fileCount":53,"integrity":"sha512-/qbS9LQzvElpvzspomWSPtzGHNGNvLCQRY9F3MAd8Dh93OyZkhmMPcFI7u5aywVu1QyiHYjZPM+DX3T+N24tSQ==","signatures":[{"sig":"MEUCIA9575tvERTvQetnQ5QyRJZiZyeQY+juB/ULWB9d5xuXAiEA9vJEkSxN3cuOzOCyosICJ0OLiQ1gjz9bxTO5HqVaDUI=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDOTk9zLMvLJNXPhfRd9dnrSrmaMCDuTVJ7gGyt9US5EgIgTYOinCTFSp31D8ev6SRkQSQ2AobDRlF1caHlF/LWwYc=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.28","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":252420},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"206aa8844f1a6c34fb2b2439948828b35c8619df","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.28","@hydranium/langium":"1.0.0-next.28","@hydranium/protocol":"1.0.0-next.28","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.28","@hydranium/langium":"1.0.0-next.28","@hydranium/protocol":"1.0.0-next.28","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.28_1789077346469_0.8660606536470064","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.29":{"name":"@hydranium/data-server","version":"1.0.0-next.29","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.29","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"c152cc283e930fe9d93bd37672aeef07ee029352","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.29.tgz","fileCount":53,"integrity":"sha512-0m+Q0D1IhZvUv1nJrYmlW1gdd6PjeTKwr6tBRq3hkBbQGeHVcg6zvCUgMUo3jUBqNtpQk2gAr+QBXEtBtOZu5A==","signatures":[{"sig":"MEUCIQDRwWiQRzs3imu4P7KdNniyQA2XLVgsgXwkt4V8A7JsoAIgWgusSgOeenIJ9xsTtPV1ysPLrrBcv74d2nOlEb6gx4A=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQDbFiR8IR6F0iT9OBkmIbtsFcLcDTImP8kFASLsaLV9nwIhAL4WO5ZGq1VaW1yNl2pGMEGK8MKpfl49cINtdf2y2841","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.29","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":252420},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"5d176ee3a002deede9bb8a02e179afb865fb8f41","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.29","@hydranium/langium":"1.0.0-next.29","@hydranium/protocol":"1.0.0-next.29","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.29","@hydranium/langium":"1.0.0-next.29","@hydranium/protocol":"1.0.0-next.29","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.29_1789080164655_0.4903478551473064","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.30":{"name":"@hydranium/data-server","version":"1.0.0-next.30","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.30","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"f21cee2e6f5b5b770c5f0d7dae8d4a52cfe2d043","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.30.tgz","fileCount":53,"integrity":"sha512-7l7H2PT6Ydc+HRwc0MeM9eogDrg+m+ZTzjHCAnUY+LNx4/2c+Duuyl7IqpunlRTIG+LjEQZlpbuyCQm9VRrK8g==","signatures":[{"sig":"MEUCIQCgu4LGzmEp8J9NP2etqI+KuQ4+biHONR8NKbtW5bAEzQIgMXUWRF/cXdC30KkcVGVS4dAre8iTLtgrtOEyXyefK18=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCKzFO7idYUhi6ZXVUz3Gn/gjhI0kG2Nnbj5nUR2ifU+gIhAJUxbH1/doaCVbwJ4mAlw36ugw3uV+DEwEKRD1b9NbmK","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.30","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":252420},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"3144b5a64521d2f949edd8796430813749fe4b55","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.30","@hydranium/langium":"1.0.0-next.30","@hydranium/protocol":"1.0.0-next.30","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.30","@hydranium/langium":"1.0.0-next.30","@hydranium/protocol":"1.0.0-next.30","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.30_1789080952880_0.03863340182984465","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.31":{"name":"@hydranium/data-server","version":"1.0.0-next.31","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.31","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"02d63cb06905ae920c28577dc51f61930728dabe","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.31.tgz","fileCount":53,"integrity":"sha512-8pM3fTByiJtGyg7au9IAiPzFTUVRkfUILLArHBBbLzBLXrs1BzBZmw4cMs9xvoeY3/1+MBz912Lteh0+a+NIoA==","signatures":[{"sig":"MEQCIFGE3+meQyd1ySrdOtj8bj8cmRrTDLczalOSEBivV2oEAiAyus+TctYtwoZzINbqlKIZYbejy9khcsaDiu8YfoMemQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDCcvsKRXR3jMndoT8XJdgsq2zpVNrsi73lDVlhvLCX+gIgGfueEhkmS/HXLhdVlle+MqxDISuBynVRDEjQ4IejIZM=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.31","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":252420},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"8e6c8c3616f7704c9fa715844ec72402a12fbe5d","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.31","@hydranium/langium":"1.0.0-next.31","@hydranium/protocol":"1.0.0-next.31","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.31","@hydranium/langium":"1.0.0-next.31","@hydranium/protocol":"1.0.0-next.31","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.31_1789081828438_0.9142772000715969","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.32":{"name":"@hydranium/data-server","version":"1.0.0-next.32","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.32","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"cbf1b9607f688dc7690fd28616f10941bcecb01e","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.32.tgz","fileCount":53,"integrity":"sha512-rg9yiEC/5ly/uuiLVCYF5RpKdC1ldnrQVKr13hnkjt3vEji6yzB3xeFxV+fhhklmx+NxbQSfu87zBhMv0b/CQA==","signatures":[{"sig":"MEUCIANJCCS1BjqF/iRddtSIvw9UaVbK7l07YCu9i6IMO3+GAiEA7tl4H2kNEMJNfYT5B5H0ke0iZEDuZSa5xkPhUxuotB0=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIDq10xvy/cu2q7toDmvED2cFy4VTh9+xFvvP5VO32sDTAiAhVt8my4KURzYzD+Ri9kSp+51TTEgL3f7AisrE0J8C6w==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.32","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":253190},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"700db3a0b4b65b843ec58b627d3c97f466fd9177","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.32","@hydranium/langium":"1.0.0-next.32","@hydranium/protocol":"1.0.0-next.32","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.32","@hydranium/langium":"1.0.0-next.32","@hydranium/protocol":"1.0.0-next.32","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.32_1789082985590_0.7370031209681047","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.33":{"name":"@hydranium/data-server","version":"1.0.0-next.33","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.33","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"8f8573aa256a3031f14633bebeff280e5bea1583","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.33.tgz","fileCount":53,"integrity":"sha512-WAyHQqWvlKrd5rtCYRlHmYKUQXcuW7RQw5xTNO+tNJWKppe0u61MwN5VmnmLSVhrn6AL1L/hWNwMxJTCOYe9Eg==","signatures":[{"sig":"MEYCIQCRsCBaS5xbPwBlgfX8KUg2NukuigjFoXAGTn9O66BD7QIhANci2ghTr2PAPDFUpNCDelGZp8QDSVOVz/zlo3DNGQMg","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIF6S35kqvkY+1oU+v07DgBo/rDb3/5kw6Z2HZddME7tKAiAWVxzqjecnZAN5/P3PZ2Rdb2aN0uxnaRxAOPIg0+kZ8w==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.33","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":253190},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"bf49242998f9f506ce89544d21740841e1f85d02","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.33","@hydranium/langium":"1.0.0-next.33","@hydranium/protocol":"1.0.0-next.33","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.33","@hydranium/langium":"1.0.0-next.33","@hydranium/protocol":"1.0.0-next.33","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.33_1789084357796_0.4176077375589937","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.34":{"name":"@hydranium/data-server","version":"1.0.0-next.34","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.34","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"c23b7536668eb3feb03fef8506eaae82774d623b","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.34.tgz","fileCount":53,"integrity":"sha512-0tUntS4HJET46YZ0ls4CxcvVOYjYApYuxsE6ZkJ8BP/dIArarAwGJxuq3zNvRqI8/kUDbVrUWYrnc6EZZHSMVQ==","signatures":[{"sig":"MEYCIQDWzx8wEQgRCgXgA0g47LdefNy54D/aOo1VuJyzLh0ZeAIhANtKfD0WW6sdgeg1GFCsjAbwkjoaNZ/Yt4aBmgTDgVj4","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIEpwiLn7BCEPUCq/EH3DZbr5HFY6nBKsEWMU1tkkZLPXAiAqbHucb2TV0YY+cG+/w+fVv0YgJgxcTUp5WqzsBoaMpg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.34","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":253190},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"ef11fbc473c423b233f3b84b1fd895c707d435e5","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.34","@hydranium/langium":"1.0.0-next.34","@hydranium/protocol":"1.0.0-next.34","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.34","@hydranium/langium":"1.0.0-next.34","@hydranium/protocol":"1.0.0-next.34","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.34_1789084786885_0.17236957212447068","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.35":{"name":"@hydranium/data-server","version":"1.0.0-next.35","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.35","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"3a9e7a17d2c821962923b73056bb77f31a79926d","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.35.tgz","fileCount":53,"integrity":"sha512-Xheh2t+cVKkeIHeaeRNih8sDBWHNPSMnMeAtkIc1wyeivh4gLjszdibBvt5PCzKSenaXHRQ+TI+s+/6xJ8WeNg==","signatures":[{"sig":"MEQCIByYVJu8PVChh/K2VrRvGVj+YmEDLm9WBM/T1n60lkZLAiAe1kMmvKiTsxWu3cInAR+KxMdhVc3fBKrcAWyPH6hkQg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCICuqP/SYfV4t/CBzy00i9shmhmbpLSPnldZUh4gKcDdwAiEA9e+j8Lu+8u/+fyMaFU0hPcRxL5rOZYVcWzYAd/qs8yc=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.35","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":253190},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"a593818fcf7c415740029d85a40c5fddc0d6d252","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.35","@hydranium/langium":"1.0.0-next.35","@hydranium/protocol":"1.0.0-next.35","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.35","@hydranium/langium":"1.0.0-next.35","@hydranium/protocol":"1.0.0-next.35","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.35_1789111044711_0.8339914365325483","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.36":{"name":"@hydranium/data-server","version":"1.0.0-next.36","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.36","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"910db246ae6dd2128e762c4f422ceab24d8e2f82","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.36.tgz","fileCount":53,"integrity":"sha512-fcoFE93e84QkYneJMPW1NLK0rscuylaDa/k/DR49255OVjK9fhdivNVeRwKF3Tp31oXUvY/VbNauKkn3umRa+Q==","signatures":[{"sig":"MEYCIQDxjQ8IjiikNZNdM1OP0gEpbfPUnk1k+Gj0auncBMeSrAIhAPFYRmDnRRw7scOXJQx1M/iGWXt5wogjUh1nHa9qeQ/E","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIBgQkmfP1fYQKkNgzLZpInqGo3SScSJYPQVFJhC6ExPvAiAm9D70YketDrC5XeKb3BkxdHR1pZOorI2u6btr5CMM4Q==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.36","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":253190},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"ecd8fd559bb737ef531c1ebb908b4a00012e6480","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.36","@hydranium/langium":"1.0.0-next.36","@hydranium/protocol":"1.0.0-next.36","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.36","@hydranium/langium":"1.0.0-next.36","@hydranium/protocol":"1.0.0-next.36","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.36_1789111549632_0.6387160490974071","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.37":{"name":"@hydranium/data-server","version":"1.0.0-next.37","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.37","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"5c4d44320ac633c1fe2ecd35c0f7295995110990","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.37.tgz","fileCount":53,"integrity":"sha512-1CbvsV8iYM0Wi/ly3HUmSXW2g4cWJ+C2awqxHgevaWq3BiJ71awk0sRi2aAn+RlUWqiCgk3noWiVu/8jyolokQ==","signatures":[{"sig":"MEQCIFVyCKG4EbG0nD8ptqWXZ67OY0/iBIjX9iLL6hy8tJwzAiBDJgf9FfDGqInsnwXrRKw7Oy+hlJguLA1PB9YKSu+CzQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIDRQV3B4fXuWcTxly7ZS58f2OuNJavZC9juLhRqphXSiAiEA/yJsTnThYNRxlN2foAMIzP3M8otmEWm/1GcigTVhcq0=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.37","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":253144},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"71281468e9eea70a91d68418d466b2c2f9b95e61","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.37","@hydranium/langium":"1.0.0-next.37","@hydranium/protocol":"1.0.0-next.37","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.37","@hydranium/langium":"1.0.0-next.37","@hydranium/protocol":"1.0.0-next.37","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.37_1789112242123_0.9370796425382366","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.38":{"name":"@hydranium/data-server","version":"1.0.0-next.38","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.38","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"3b7ad1323ebabbff3bb389b5a823093c3cfa5913","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.38.tgz","fileCount":53,"integrity":"sha512-Ih4ZD647ChQg9ukKeTotuyFzHCZeo/T7HkzWLquAQ1NbwjhgdHavgCb+9DsclTogHOxszOKV/n+IxNetmbQyAw==","signatures":[{"sig":"MEUCIDuudYAPSlm6RUGSMEW1zPNV2gSqarkcGVHX+OnwXv0EAiEA66EcZXof9IsSiVHExnaXe/N+Qx9wKDMzRVCkLU38QT0=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIFm2QGp3B4F9WZKg3KkxtGwBk5h+QR789ZXIidGztwI+AiAp0YrJ6Q0+yF7cdszXuWcxyDvQ8Ta7PmdzxWq3A2G+cQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.38","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":253144},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"0b55576ebe72990a6f20c437cb4e0206d0da7265","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.38","@hydranium/langium":"1.0.0-next.38","@hydranium/protocol":"1.0.0-next.38","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.38","@hydranium/langium":"1.0.0-next.38","@hydranium/protocol":"1.0.0-next.38","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.38_1789112625064_0.7658312298772278","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.39":{"name":"@hydranium/data-server","version":"1.0.0-next.39","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.39","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"974b351f274a4a22af0772fc621fba32b837b2bd","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.39.tgz","fileCount":53,"integrity":"sha512-rwtjqc+ntsKMv0Cmh8vJ/HLSIHmbxRPBFqaRmhNsmU3haEPhdW4Y2z8ErxY3jN8R5CZAIGQc8JNaF23tAT/uSA==","signatures":[{"sig":"MEYCIQCacxlWhAoSIVNqVhneHOlUaucpsD3Hp9noCWvZTMY2aAIhAJczyayFuEOF3YYmjtcb1mNW1m+Y8zdBoTOc/+lC0Ls3","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQDFGwHAhCaMTHWIPrtERN/EBMiokVmmMzFIIqoPXspLNQIhAMBB48saaPyXFHslK+Oh8iK3k5aknQQ0Q8B2zksycUYd","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.39","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":272950},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"85360c20902dea3a7e75a1816cb2b66bccc4a8b8","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.39","@hydranium/langium":"1.0.0-next.39","@hydranium/protocol":"1.0.0-next.39","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.39","@hydranium/langium":"1.0.0-next.39","@hydranium/protocol":"1.0.0-next.39","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.39_1789114075021_0.7880514037868751","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.40":{"name":"@hydranium/data-server","version":"1.0.0-next.40","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.40","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"43a5c852438236ecba963ba2a965c197c3a92aba","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.40.tgz","fileCount":53,"integrity":"sha512-fDw1sQUcqLZ4DzhJyrLwUWCTkOUHrCD7+I8TbDiSw5M0qmjBiSZrSbwjiUUIjSZd3ylghWy2BkImHx7k9Y9Uow==","signatures":[{"sig":"MEYCIQC7ApqwpxVXUbdzlZvF36va84iEvZ2z8H2YiUUT8Eri6AIhAJy1RoTbybQRal3/PFHzcBZQfwfDv2oQvcBG47Ps1Gdq","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIDINcf1cfm6HXTdZJ95UyJJ6F+JN6g+A6c/KJUiqy/NTAiEAjyWiD0eRglOVcrV0VhWTGvgeD1YlFjadUENDbOT1Xn4=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.40","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":272950},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"bc342467f388397ab8033e70fbb8af13451a04a9","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.40","@hydranium/langium":"1.0.0-next.40","@hydranium/protocol":"1.0.0-next.40","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.40","@hydranium/langium":"1.0.0-next.40","@hydranium/protocol":"1.0.0-next.40","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.40_1789116652427_0.3501361533644398","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.42":{"name":"@hydranium/data-server","version":"1.0.0-next.42","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.42","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"1331562a0bb3b13dc8cc4f41d52063cc2bff800e","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.42.tgz","fileCount":53,"integrity":"sha512-9jRTP/wt0zNz6WIJkhxs4UkRieGm1fLMY4YxPO3SsQ4FVT2uJBzs5Rxc8HBT+BVQJmr39UYrwMitQ7oDxKNpIA==","signatures":[{"sig":"MEUCIGCfPy2QqhvPWg/9Fbm+9rStyogm7Lh5HGyvQ+XohKtXAiEAnk/4gxZrpNlZFNcSMGnHf3RlQt66oVNrDCoo8/mEpNM=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQDYBef3NCj8gapl/NQDid8HTD4lNFQIP7fAJkOuLGgy5AIhAOBX1y3AL0eYR4CGrJ2ve6N+kr37LgEhKZQMTisWYRap","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.42","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":272950},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"1c0395351d8cf4bca5442cce3721b8fa4d7f5177","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.42","@hydranium/langium":"1.0.0-next.42","@hydranium/protocol":"1.0.0-next.42","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.42","@hydranium/langium":"1.0.0-next.42","@hydranium/protocol":"1.0.0-next.42","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.42_1789123595262_0.6579875051903692","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.44":{"name":"@hydranium/data-server","version":"1.0.0-next.44","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.44","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"a5d82a6d35c7a1879403ef1dd61c63a51842a637","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.44.tgz","fileCount":53,"integrity":"sha512-699YOOaibZEJqU1NpvyWbK+NNhUx6oxGW0IS7KZBT37eDCMlsiQGYeb4ztCsHW7SMcj+rV2p35QMR7T6PV44Jg==","signatures":[{"sig":"MEUCIQCXKvhsZrnXTO7ARKPFFI5H+zUM2sb/kZLyIZqIui3tNAIgIrvvxqtJrimwOT3vG43Hnkezd5ofZwQbFyVoAJZsoLo=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQC2JEdGtbk/q/xt/VnRGZUwvfRWZkRxzeMw1xYeUeDLDgIhANgsQ72/BJO22dEhHKTPSCTmsmK0z40mXiJl3eH/6fw9","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.44","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":272950},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"d422b97846df49ade27fc9f59c971520dde807fc","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.44","@hydranium/langium":"1.0.0-next.44","@hydranium/protocol":"1.0.0-next.44","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.44","@hydranium/langium":"1.0.0-next.44","@hydranium/protocol":"1.0.0-next.44","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.44_1789128177570_0.293461252855465","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.45":{"name":"@hydranium/data-server","version":"1.0.0-next.45","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.45","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"80f902c2cfca87bee40bc3f74ad11946824a55f6","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.45.tgz","fileCount":53,"integrity":"sha512-zXE4UC+2PFk9I+ZBWn3KKpvFQb5MHeRCFljwrvf3zIh7uooj+GdzD8zxrdEd/bsUtsIuyMhvTi+oFMWM53FLJw==","signatures":[{"sig":"MEQCIDEXMh75Vy6pdhmIiIB5oSERlVPfj+F3N9/vy4G6SZm5AiBvanuHoerqk4m+I8vS93cf9E02uLwcUoGu0TihEoXKPw==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDgGCoRJMSIjTEynn+rA5R06L3A6dlOY4wJe9UCeJumFAIgS5yZFhI8nj6FkzWjcxRDHyo7KcvGQ+95KufTkgSrAck=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.45","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":272950},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"0c2e2da8f3afba96ba16fc3a98115b3cf5f1e0d5","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.45","@hydranium/langium":"1.0.0-next.45","@hydranium/protocol":"1.0.0-next.45","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.45","@hydranium/langium":"1.0.0-next.45","@hydranium/protocol":"1.0.0-next.45","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.45_1789130136976_0.5822274773878093","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.46":{"name":"@hydranium/data-server","version":"1.0.0-next.46","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.46","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"9b6be48e6d0dacc6ddd3151944fa96e72d3a4772","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.46.tgz","fileCount":53,"integrity":"sha512-8QORQFx/MvTr6VPamkDLh1UNzkdczSN9nMNjSsVXePoIGAwMyQy7YRbTrBcZjJuwjOgRmFW3DgVEQ1E9ON2qkw==","signatures":[{"sig":"MEUCIQDc3p04hGOC4aXaAzfVo3N16ItmZFsWErcHfWEywkW4fwIgRvdxPLvGYZcCc3P5Af6nFanafnrOLiJG/s1yAsRFuJA=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCICqgj1bfFdbkQtshAUds2l0GiQqb/K/nJ/dezISYiXzzAiEA0v0hZFA3Jltn45Ja/3rEJLgqO53oKrHIS45PFWWoK6k=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.46","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":272950},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"df83b12d3657272e7bd994bfeb01953c9b30a8ec","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.46","@hydranium/langium":"1.0.0-next.46","@hydranium/protocol":"1.0.0-next.46","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.46","@hydranium/langium":"1.0.0-next.46","@hydranium/protocol":"1.0.0-next.46","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.46_1789131913537_0.7497569969942897","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.49":{"name":"@hydranium/data-server","version":"1.0.0-next.49","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.49","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"7d0ddf65655d38f9f2c7449925f3272da8e00106","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.49.tgz","fileCount":53,"integrity":"sha512-XsCE1QAr8dfFlVh1fMQRyS8pDkWUxO3su4IIZL6zFp3iXvMkexHGVpHRBQdNiKFRo9bCSfLGx00QYxOjozIJ1A==","signatures":[{"sig":"MEUCIQDxAdV9Z5sEYcutKoQjdDnAnGyZzRuw5IxBPGtsAjqUhQIgDA4zc57szs2xvMAzJlEF1YOjzGzQzJEf/tOWHjMFfNc=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQD4l1GmL2uf8JaA7amq13EB+aoU9D5MKCJsVZeJQO4SXQIhAN0FTmri91ofHtAxvS0V6CF/pLyhpbX9Udc/IuHvkBGK","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.49","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":272950},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"b08c1dab6484db2bbbe43c3e07db79155901e217","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.49","@hydranium/langium":"1.0.0-next.49","@hydranium/protocol":"1.0.0-next.49","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.49","@hydranium/langium":"1.0.0-next.49","@hydranium/protocol":"1.0.0-next.49","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.49_1789473588731_0.24874597559267642","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.50":{"name":"@hydranium/data-server","version":"1.0.0-next.50","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.50","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"18710ae2b14d8f01cb14cffd57cf4cd3fb19e52d","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.50.tgz","fileCount":53,"integrity":"sha512-powoA+9WzwxPF7CI3+dXxGzeu8Ku8W1k+j+JmU+a89woU73ezM34wNDpxyvcnyDOlKM3mNn1qvbAO4y/94yJpw==","signatures":[{"sig":"MEYCIQC38LVAXTDeskzM22qC5BUX35IUMjCoALfOXGqIDVtCGgIhAOyfu6npRRAzDJCwOiD1u7ghzFP/0q7LVSUBOwISJxXy","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIAyjJKTEDe13cTVeA6lJbZyi4wbX/H3QJb5DBTrYdakZAiEA59b8cuetrukQVKYM9T9inudYymlPFoZItNvv9n2eeLQ=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.50","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":272950},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"2e9b935ebe05c3bfb550a411f09668c28903c603","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.50","@hydranium/langium":"1.0.0-next.50","@hydranium/protocol":"1.0.0-next.50","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.50","@hydranium/langium":"1.0.0-next.50","@hydranium/protocol":"1.0.0-next.50","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.50_1789475794528_0.10887639237537083","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.51":{"name":"@hydranium/data-server","version":"1.0.0-next.51","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.51","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"785902a8327dfdc59f40f15454628e9fbdcbdf4d","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.51.tgz","fileCount":53,"integrity":"sha512-1zqE+L1PB3yHbVP6bieQWTizVxGPVPUaMsf9HWhZmmgT+BfnUHqm33BXoWwXWoAL0VU22xIFbwZ6i50yIsuEbQ==","signatures":[{"sig":"MEUCIFhMZmf+TGFTbBO+8N5VctHHFZkQtRKVXMUlhu5RwCKqAiEApjDUI1KzyawVuWUrEhWmwm4EzWEIn35kcLIrN9m2eqc=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIDgU9gAgOAma5BZ2DNR88xBY4tEFS4tQTbH4ch8NwLxvAiAuHw05WfrTUIHMh8ZyMjL5kBsp1yV5+FLj31B9gZyZUg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.51","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273012},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"5f38a70ec703c96b9211f2632ef9c64b4d35a0e2","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.51","@hydranium/langium":"1.0.0-next.51","@hydranium/protocol":"1.0.0-next.51","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.51","@hydranium/langium":"1.0.0-next.51","@hydranium/protocol":"1.0.0-next.51","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.51_1789477026520_0.5944354364362252","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.52":{"name":"@hydranium/data-server","version":"1.0.0-next.52","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.52","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"705ab7c9ceef08a5f41c81c05b417aca5647780d","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.52.tgz","fileCount":53,"integrity":"sha512-JpwCwLa3aJ1sK+6JmdjjfmPqec55LC8YQDEjI0ziUd/a1XRqHWJxkp4p/HcIPuuD5bNW0eqR91Atuu376+Hurw==","signatures":[{"sig":"MEQCIFd8Cy89xXuNZKKPfNWTEBSSObJ2yr+5DtnBsLFiOPsGAiBZaN+640vMgS9c5iFayZyfRUx8E4bI6paBfv8Nzjmeug==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIDFNP7IB91ifcRlgFpaOzc7fHLe1r0LnZOKGGoSdrionAiBmV9LpfcxzI/bpyaYfgJAO4UatwMGppjVEcomPx6lfjw==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.52","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273012},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"de17637218123da3f6f1393b3f3303178fabf878","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.52","@hydranium/langium":"1.0.0-next.52","@hydranium/protocol":"1.0.0-next.52","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.52","@hydranium/langium":"1.0.0-next.52","@hydranium/protocol":"1.0.0-next.52","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.52_1789484155185_0.2996478563214515","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.55":{"name":"@hydranium/data-server","version":"1.0.0-next.55","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.55","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"a419c20653030891629b33968cecceab4fd1c229","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.55.tgz","fileCount":53,"integrity":"sha512-jwsiE/mhj7tWp3bLIRUpF79nVkFHQvHWdhIBQP8uYnGEDdgRcxi6NxGUImlbtXVaPlWsNBwEDl1HZn+Oq0bDBg==","signatures":[{"sig":"MEQCIDhUWklVT4rgYcKpdOmrsFo+owil3tlz4Z9cBERA1kmnAiAMZ21hAkMf0xsCJYIWFpTzLE31sptSnj6i00VLUzqN5Q==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCyZZ4GWP9v+nFdvDJpdlC3OzqNOT72EUUfw6JNPnajHAIhAPZcbgMXY7aXymIdleBV6u2FJPkHDeWSRPUAo0sVD3CY","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.55","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273012},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"52533e6c56b9f7c07bc3e90ed6a9fa00dcc17b65","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.55","@hydranium/langium":"1.0.0-next.55","@hydranium/protocol":"1.0.0-next.55","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.55","@hydranium/langium":"1.0.0-next.55","@hydranium/protocol":"1.0.0-next.55","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.55_1789563536234_0.5130989825624903","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.57":{"name":"@hydranium/data-server","version":"1.0.0-next.57","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.57","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"e3ccb5e1c6f94b03468fb0497cf59bd9d32a7dad","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.57.tgz","fileCount":53,"integrity":"sha512-lH4Y9A/jPHr4HbJwTLcrUTD7R/jdPvBmbzPHnS1iSI5lDBe+OGSgOZruTNTCwg9LAvLnrvhrm+3GNwxtGos1/w==","signatures":[{"sig":"MEUCIQC8LslaNor9VORdw3BUSUYr/Qr9u2SjTqBl9wrK7tf9JAIgSWlYElXxavyrno+M2GJwz/wE2UXAIunTMWBBwUTFYSE=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQCEFQbvSN4TuUzWK15QV36NjE/+sxqBhFbWg/LAxTGcrgIgI+XYINqWmKIPnwN47E5QD0yR358/iVU2MLXDu3CJMIY=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.57","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273012},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"8e614f55b457c6f8a5ba228ac58d24f210126eaf","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.57","@hydranium/langium":"1.0.0-next.57","@hydranium/protocol":"1.0.0-next.57","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.57","@hydranium/langium":"1.0.0-next.57","@hydranium/protocol":"1.0.0-next.57","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.57_1789572760122_0.34976531311005044","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.58":{"name":"@hydranium/data-server","version":"1.0.0-next.58","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.58","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"952195e23a799d0c6074119de7fc83e549746f97","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.58.tgz","fileCount":53,"integrity":"sha512-ae8TMwYfkjM1CMv3p9p5ybAh3eA/PHbiHYP7qrFuBPtVI+RivP3W9WF1oopKmF7FNyg+eBdjAfnuLaUrTFwuMA==","signatures":[{"sig":"MEUCIGg4X7JYjmHBFny5flW4A229c2s8JTO8fS/e883MgQDjAiEA3yrbsW2CoUl5Y5ogAKgP99Z8pzGwkbXVZ5/E4NpStHk=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIE2ocHQq1SScuin3baUVdzSBOaVgSsGvoEAJ5atN6A1RAiBlhULQXhAKPp2f88KDsXAQzNblVjRrZiSAGT29S9rHcg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.58","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273012},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"e11d975dfe5c1946333588c85f2539b2ba0b8831","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.58","@hydranium/langium":"1.0.0-next.58","@hydranium/protocol":"1.0.0-next.58","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.58","@hydranium/langium":"1.0.0-next.58","@hydranium/protocol":"1.0.0-next.58","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.58_1789572988647_0.08547337935380206","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.60":{"name":"@hydranium/data-server","version":"1.0.0-next.60","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.60","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"dd1e0a6dbda6c5e9ddd805fa6b5c9b0d0717e88c","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.60.tgz","fileCount":53,"integrity":"sha512-IdM/j+EX2uux1Y/Mq/uGCpu/SV144SEw0y0S6+cRETh3wZ1HbApQJnTgnqiRhxMjMCshtKGBZWxZ3ZkDDeNLAQ==","signatures":[{"sig":"MEUCIFjnyUp2LQx5XblVjZXqZ1UQXa7Pz+Tk+ms45x4zjQoQAiEAvtSqFWwO+oiQrLAd6cBgKiGfzRhXuEpD2TMxjpstVf0=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQCciqr0rWXL6VNNu07tKzivQ+NYaJ+wPBMAxemSMyWCVwIgcuhAzldmuYDtRhIDKo382NUFoQsb1wfDQ/EtPeQ3VnI=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.60","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273012},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"0e89e5480ccac85e072121bcc4280e4f21b6e5f6","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.60","@hydranium/langium":"1.0.0-next.60","@hydranium/protocol":"1.0.0-next.60","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.60","@hydranium/langium":"1.0.0-next.60","@hydranium/protocol":"1.0.0-next.60","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.60_1789634930162_0.11906151621471794","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.61":{"name":"@hydranium/data-server","version":"1.0.0-next.61","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.61","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"0b449ee539fd722128542a4d0b353d29b7b5fbb0","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.61.tgz","fileCount":53,"integrity":"sha512-0qTCG02IEDriWUynW3fJrHr4KtB+Z+ZiR7biqfMefSesIlmdGpOzhwrXZEMHOswos4GY8aNYOn36oBjtUu6QeA==","signatures":[{"sig":"MEQCICxyxQ3hWZCJJ7xZnGPFldEBe9uIXTQ0NkqPdlECIUfTAiBzKhw0COSCF6lp7kjIIeY92qOKE/37QSEpctIDVHDjlQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDJFc6S7IQodJCb7G04W9LIAjDcCa5EiYo1U0UG85tsiQIgRZpVqZrW0pJwERRA6uDOBx+evv2IlNalHw2Ka4XuWyU=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.61","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273012},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"f2aa66b54903e3b3e4932430bdc99503f5ce36e6","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.61","@hydranium/langium":"1.0.0-next.61","@hydranium/protocol":"1.0.0-next.61","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.61","@hydranium/langium":"1.0.0-next.61","@hydranium/protocol":"1.0.0-next.61","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.61_1789643265483_0.1031776146121377","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.62":{"name":"@hydranium/data-server","version":"1.0.0-next.62","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.62","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"db80a8fe83116da324c35e30f91fe0f7ca870e97","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.62.tgz","fileCount":53,"integrity":"sha512-KvLYoAxCrHmQ5RVwhzdoV3aR68SS4JwA5QnAooh1S182CWVDEERrZIw1uTuY7E1fqieyWmLoKOQpnUgWIQI44g==","signatures":[{"sig":"MEUCIQCiumbDjwJpNAhrVSDyGO9l4rYUCzG3yzrFmUO3g7gk4wIgGaDAXBM8rdeD7d94HC/xE5dKebKd+OC0U+XV5gN7ScM=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIANcAw+l6U2PAoUfvI+68+rlcDdRrDxGLOHBrsZY4eZPAiEAplkGzD6Mpe9F6WlklG9D0KyfZT2TVmc//n4B8Raj+dE=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.62","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273012},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"6246734b049f5d6029ddc57bfda9ad0c234ce11e","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.62","@hydranium/langium":"1.0.0-next.62","@hydranium/protocol":"1.0.0-next.62","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.62","@hydranium/langium":"1.0.0-next.62","@hydranium/protocol":"1.0.0-next.62","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.62_1789650947279_0.6960004435712934","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.63":{"name":"@hydranium/data-server","version":"1.0.0-next.63","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.63","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"f8b37140cdb3c5355217309c6fb2f3c896c217a9","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.63.tgz","fileCount":53,"integrity":"sha512-GMm5unw1bj6Z+X6++NhlMNhZyjUbLHwoXZ3kw19sBDzKVEoFbhecxYtLcj/BjYS7pK7NbEvPLjJ0h6agob/MIg==","signatures":[{"sig":"MEQCIG0ndClR9kuwpbdbNsxr3vWdHeB9bRgN9RX3CdiVdLaDAiAamrIzK61P4fJ/JdV6lJQd650Q90733hLT9+m+lSIVPw==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQCxxwFbeLlveb4102b637QNHNoL5sP457qOXRI3GVeZPwIgYGQvEKcR9qTkjtvAabi2XoRBFZPyXCai8WCieUlDILg=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.63","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273008},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"b5aabccfde4752da8e1efd4017b822eef531559d","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.63","@hydranium/langium":"1.0.0-next.63","@hydranium/protocol":"1.0.0-next.63","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.63","@hydranium/langium":"1.0.0-next.63","@hydranium/protocol":"1.0.0-next.63","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.63_1789651401918_0.6043221394191876","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.66":{"name":"@hydranium/data-server","version":"1.0.0-next.66","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.66","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"12a8d8fcfb61108e55eaccef21a65f722b70338d","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.66.tgz","fileCount":53,"integrity":"sha512-huRPMYDGbxO9YPxTDNqxl9jnfIweoNs8J3mH//msexBGmaRWOPmQv+aGL+2okCRXppXXKewdAZIBRTJL1s205w==","signatures":[{"sig":"MEYCIQCjrsVvkviFTPnAm/4U33t4lwJKBKSnK+SeoEh+h+tMWgIhAKwG31bDnWcN6foWzgqMzOuaock42UWC4wGlnksI9l2E","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIFHvrpWye4ISbNepaCjYEiOczBC3LIRcLV2AuB5PmaMrAiByZcfj/Y/paa8gHWX3H9b0ZZwcWLRc1BXkkwX/bqi0ag==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.66","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273008},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"5f76b281e64b2afe365e29c49d7388f20a626482","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.66","@hydranium/langium":"1.0.0-next.66","@hydranium/protocol":"1.0.0-next.66","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.66","@hydranium/langium":"1.0.0-next.66","@hydranium/protocol":"1.0.0-next.66","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.66_1789680443706_0.26893868635778784","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.67":{"name":"@hydranium/data-server","version":"1.0.0-next.67","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.67","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"2611788e79c7d6b6fd65f83e0b155fd5267a82dd","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.67.tgz","fileCount":53,"integrity":"sha512-JouMba3qOYyhZ0bgqMH6COmwwbMh7xFMfrIJcrr6vFj2FhU45OGjeIbjP5dOkrcdfrPFS6YFa8pBs64fN9XhpA==","signatures":[{"sig":"MEUCIQDdDZDC4mnUs0reurm+1XwEEkBBxLn8XzYx4P71DuvtSQIgWhcAECqoZs9DwlbN/puezEl2KC2IsOLU7QpSppQmiLI=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIADHvLka+SBdZgQiSyNdVncofECv7+uw/vVo1Z64TSxHAiEAiD9JcGWVMkzdqyDu3DakIhY09FwZpsRIqcpFXcZ3mq8=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.67","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273008},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"f99034d60a4f6cd850b7a97db6f52cef729a7c23","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.67","@hydranium/langium":"1.0.0-next.67","@hydranium/protocol":"1.0.0-next.67","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.67","@hydranium/langium":"1.0.0-next.67","@hydranium/protocol":"1.0.0-next.67","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.67_1789718001047_0.7447474291854581","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.70":{"name":"@hydranium/data-server","version":"1.0.0-next.70","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.70","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"0104415d2794fd664458a60f5304be128e87b1e9","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.70.tgz","fileCount":53,"integrity":"sha512-TMqcRdq/aP8mXdkvEdOETspgNwlepwPYG0UOq2etKfupCjyb32mMeCs+2E39doZDGBPyWvQxPUkKvzLon7sXiA==","signatures":[{"sig":"MEUCIBLkWU0wjgmPw+Ma8JkBz/oxyQe118Z3SUGM3p+UQxN7AiEAgsmA7WNQrgTjIj9pTSqYP2uXS157dcOx+nnbaodWSGk=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCLrecmdTPjt+tJmkQS3S6MhoT4TvmYIROpO5wmebfnhQIhALFe/Fntyw11Dqu7tTf8UFEa/niE7i87pudfBI/Fvw6o","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.70","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273008},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"0f9f85df8f69447cd97a9215de36328761f79b1d","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.70","@hydranium/langium":"1.0.0-next.70","@hydranium/protocol":"1.0.0-next.70","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.70","@hydranium/langium":"1.0.0-next.70","@hydranium/protocol":"1.0.0-next.70","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.70_1789729543258_0.44867156086763904","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.71":{"name":"@hydranium/data-server","version":"1.0.0-next.71","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.71","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"e49e23e42b347cebe2894adada78a8351b0ff8fe","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.71.tgz","fileCount":53,"integrity":"sha512-xXHKUR3/TUozEDV7HGZKXSH6F5/T1VV+0A/qJ47zdiV/3c7i2pa7fiz+GYnPcyHk6yOYM52rpR2+CeQno4GOqA==","signatures":[{"sig":"MEQCIHXhHB9D8o9/FRHeh8Q7zdmrzf/b/sCMiA1KZZ53N8ZyAiB9MEtyekceHTu8aDCeGPHl4V/NcGdx0do+bUK5yWDYjg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIBJKXyH9dtAZw68PDpBhvHJAsnHLSQONmvztmmoWTVFIAiAQ9texVBrWrrCuoEzz5ea+jM8iQqwjViswAEVw33sUlQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.71","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273008},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"604975444cb71f9dfbf2fd24c069530608c86941","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.71","@hydranium/langium":"1.0.0-next.71","@hydranium/protocol":"1.0.0-next.71","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.71","@hydranium/langium":"1.0.0-next.71","@hydranium/protocol":"1.0.0-next.71","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.71_1789730237741_0.9330599499088483","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.72":{"name":"@hydranium/data-server","version":"1.0.0-next.72","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.72","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"d1ba91b5033cc202ed37f85eb2f8a0b5aee4cf16","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.72.tgz","fileCount":53,"integrity":"sha512-Ezc8rkFpDeVthYGQ/LqOEoGGNnJgUFiMwaWxiu5xMzlNH3JNTzYTe8hVWvyDHKDPVoHF+6fLPvVhx9uSIqEF5Q==","signatures":[{"sig":"MEQCIFZqMzMcyIjpn3pyLs1OohS9yTqAsAOAQ23WgO82fqq3AiBf8JSvGGbpWMd87QroyPNRX+cZiYha2an5APB6+aaUUg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQC9ZgX6qn47ShCHOZSkho6Vh6E/ONpjlrwGAC1K652bxwIgIan52ig49A1GBb/XKgOtse9n8L4CMwXqP7SiaFt41Bo=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.72","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273008},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"bb5c11b2465938e4a268f5fba57e1ef5ca5304de","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.72","@hydranium/langium":"1.0.0-next.72","@hydranium/protocol":"1.0.0-next.72","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.72","@hydranium/langium":"1.0.0-next.72","@hydranium/protocol":"1.0.0-next.72","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.72_1789735313567_0.9163207398444151","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.74":{"name":"@hydranium/data-server","version":"1.0.0-next.74","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.74","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"1c8024afa1046a3bd45850c1e63c814e97865fae","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.74.tgz","fileCount":53,"integrity":"sha512-a3IsVt+3zeF6LkQsmA37tCjw4JlNnmW3ZEENxlu739ARJXNtidBfs+zZTf7Fqb3V6KRYgyigBj76gFbg0hXQkg==","signatures":[{"sig":"MEQCIC9hvx7VybZ/6ygPuAibdYaG6JprSS3vgeehU07oXwO9AiB4YskoaMHV+u4evK7URmMhdT39jr+Bnb7opZhHN2rNgg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIE0Z+bfWBAz3KmMPwDTXXGHHsnDCMaYIoudPUsPstUqwAiEA0FY4rJMHTGs4KfiztnIoJ/4QK0q0PiXXSpvJSbaz//E=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.74","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273008},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"5c8600ba0b3c4f306d259bff5ef13f0498d04560","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.74","@hydranium/langium":"1.0.0-next.74","@hydranium/protocol":"1.0.0-next.74","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.74","@hydranium/langium":"1.0.0-next.74","@hydranium/protocol":"1.0.0-next.74","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.74_1789741358698_0.08750731486887497","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.75":{"name":"@hydranium/data-server","version":"1.0.0-next.75","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.75","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"14bda76d1188783a6503461e857fe1b4628b294f","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.75.tgz","fileCount":53,"integrity":"sha512-zS14QaX2pD33m2LyxiQmhi9gXZ6f7fOwZsijDAoUwpXU7lJy40cFoatDtcUGgpgwwc3aO8nHFbwdHUxGyvH3sw==","signatures":[{"sig":"MEUCIQDFEKi3P+ZQeu+Q9tgnWT4ZGm1ustk3qaogLoESAXOtZwIgG0sEC/Y9SlWIXRIPg2qqN5D8xhDxRLUOrf/f47UVPW4=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCID52MNFPo3xzx4X33usiLH+XttTT8x/iGUnupjb8g5EhAiB5CfpG92pE+Lw4WK5SrIz7TBI2PdevfhpkLrlNYYKFxA==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.75","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273008},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"8f3a13edc12662d38deeae09af0de9416064abb7","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.75","@hydranium/langium":"1.0.0-next.75","@hydranium/protocol":"1.0.0-next.75","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.75","@hydranium/langium":"1.0.0-next.75","@hydranium/protocol":"1.0.0-next.75","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.75_1789744201683_0.6992167925455413","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.76":{"name":"@hydranium/data-server","version":"1.0.0-next.76","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.76","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"c7d49d6f2767fe2d08d110de101e06d80b144b6c","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.76.tgz","fileCount":53,"integrity":"sha512-9yiXKZcmgn3JJi2z3kSvH9V5si1XvwUXNBUESDq3KAwA5n6BrvR6Rm7ciPj56uwoRW/69rzfV3zmknnpMqafXg==","signatures":[{"sig":"MEUCIQDWiTrKS35F7fnWdJ7lboUXh4hYINGrm+IqxjBuAqaZyQIgDqpDYWSFStkUzKDq3rrMY8p+PtCdNw8V0rrFTl55YEI=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDAFJMDdRGyZZ2DRZBHvHsK86zqL8EsD2noA6nPifi7JAIgDcPVuncoJBNhwcw9D5Wfagyrs1lv81ft7kX1draUqms=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.76","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273008},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"0a65355f9d54e10db62c1c84e8e5af24e480a164","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.76","@hydranium/langium":"1.0.0-next.76","@hydranium/protocol":"1.0.0-next.76","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.76","@hydranium/langium":"1.0.0-next.76","@hydranium/protocol":"1.0.0-next.76","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.76_1789765058425_0.3344990521032227","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.77":{"name":"@hydranium/data-server","version":"1.0.0-next.77","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.77","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"4633e6e881ac97fe2f943a5148d1bdd06c44c0af","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.77.tgz","fileCount":53,"integrity":"sha512-+shbOSoL9V8reJfS70tigIzUxjvuFRCEGb5L1EHXGAjZdhb1lbXS/WNZrOl2qFwE50c8pEVCfpOQpa0zn9dsqg==","signatures":[{"sig":"MEUCIBTMqhtAilMy2BGIqBL0DPPqDxNHRcSnyl1tbT3i9+51AiEAo/kxt4U8YH6VDX2R1hqE2ZE+ZTa9gRQUT3ui9My8Mas=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCFdUkjK55dTBEVs8bxKmp5MAMD+PvRo0lXCLGoHayLBAIhALcYocJKKw1eRESjL9fL1KGjeNo8yjgE8C9VVwPAP3ja","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.77","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273008},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"04a881987b50020f2d9948d8b7fd8a2f56483007","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.77","@hydranium/langium":"1.0.0-next.77","@hydranium/protocol":"1.0.0-next.77","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.77","@hydranium/langium":"1.0.0-next.77","@hydranium/protocol":"1.0.0-next.77","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.77_1789768639947_0.10157655762357343","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.79":{"name":"@hydranium/data-server","version":"1.0.0-next.79","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.79","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"fbeba99494acc0d85ddee17fdc78ccab784e5b10","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.79.tgz","fileCount":53,"integrity":"sha512-O2QglMSeQujsyRspRDIABGJwwri7LJ8/CzaFIvbNGJJBVwQj8coMncoHSyNT+d4QtKyAzRSW1xmtkEkndbYYDg==","signatures":[{"sig":"MEUCIQDbwa7UqBKTvr2DRM8NHu74T4SOUc4ve4iOBBUcU+DXngIgUPti8+OKZERvNVVh0MDtnVJjo14TvCMx/GcQ9nQaE+U=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIDGoZIueprunc8lUiM3ZdDTeT3x5yZsPWpCVUagJr38cAiBcxWIHh3mYy5fkuRDryxii75k1sNq8SjnILdMR8TyKyg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.79","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":273008},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"cdd4ee08dac5ead84462ccf4e20b34a06b37953f","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.79","@hydranium/langium":"1.0.0-next.79","@hydranium/protocol":"1.0.0-next.79","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.79","@hydranium/langium":"1.0.0-next.79","@hydranium/protocol":"1.0.0-next.79","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.79_1789916503838_0.42087943405785433","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.85":{"name":"@hydranium/data-server","version":"1.0.0-next.85","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.85","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"8572cb8342c00e0f615af38980cf1f229b0101c6","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.85.tgz","fileCount":53,"integrity":"sha512-Gv/JTNrR89v/5/y4LTjU1rkHGwMOtRW9bigO2YFudJRIjfTdXDxus9c860IAg38YpAVl+CWeSRE/ijZbtDMsfw==","signatures":[{"sig":"MEUCIC1Bjofq50aQ50Fi+juwY6BGtDsZdZbKP1KwbiA+ybJxAiEA/qcgJQO8AX2RWDahvyiRr7K1mhPpEa+Z3anyJW5V4cw=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCID8w0vrU3KuIA1qV8ojN0NnEIoFDSogGNVUCEGAeaUm6AiBk3DJbJ8c3nyGzjrDC0R365J6FGzITyBO/5+857L3DQA==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.85","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":272941},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"fe5acd004ce128c9ab614e06bb4ba246cfbf89a2","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.85","@hydranium/langium":"1.0.0-next.85","@hydranium/protocol":"1.0.0-next.85","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.85","@hydranium/langium":"1.0.0-next.85","@hydranium/protocol":"1.0.0-next.85","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.85_1789939364862_0.16281026874768467","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.86":{"name":"@hydranium/data-server","version":"1.0.0-next.86","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.86","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"20efb2c1cbc2767fa5b30ee9889078b6b28d7490","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.86.tgz","fileCount":53,"integrity":"sha512-efPMolaGeoHbPnyjUX9y7CGG0dWRUFRobtafCgDCe5ORDeYeeQm12CqDXoMuFSlXbzogIqa9d6njkDrW8VwYsQ==","signatures":[{"sig":"MEUCIQDVAoh/UQXhNu20rLMevWlphK3Ct13fLsLbqsIuwS/XSAIgAx+hIQyWy3kfw/VhWXFS43+IQB1OE/NkcHVnbcRJ4ek=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQDcCty4wvVEmRtQdEVBh8nJL7o1oKKHYj+ao12/5hokigIhANaXz+yWoU5mLClbTUY0TS6LW2Jh55ES+aV6/rwQYH8J","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.86","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":274814},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"7cf16c55fe7183e87b9a24b9f01cb76ac6095603","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.86","@hydranium/langium":"1.0.0-next.86","@hydranium/protocol":"1.0.0-next.86","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.86","@hydranium/langium":"1.0.0-next.86","@hydranium/protocol":"1.0.0-next.86","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.86_1789974895059_0.6201399974066701","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.88":{"name":"@hydranium/data-server","version":"1.0.0-next.88","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.88","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"3e67b8cc2e5c32ad0b03851fd3037ce3abf5d280","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.88.tgz","fileCount":53,"integrity":"sha512-q+n1JUyEurCBTVGGzH/vIOp+65QWT7N8sHQoBAN2/apURsEl26vEZX2Vm3XWwLtlbd0kpwupyc+z30G9KUSpiQ==","signatures":[{"sig":"MEYCIQCn5zyLo+NA3oKIYXrJ+LoLu9Ly7i0GaTg3oOKn6ggxcAIhAKQ98n2wWz2/ASqyj58yQ47mr/e5fsNlTU3YV72x7OMM","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDllrTqnZaVs4vIUbLt9TEPXgTvKS6CmxIbtqkWIPi7dQIgWK67Gga26FaISq9pWo79zUX8TgL5RyV/AKts5O9tDEI=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.88","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":274814},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"b3ac9a4c60d83edb3c0e53e8b8afbe465607331e","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.88","@hydranium/langium":"1.0.0-next.88","@hydranium/protocol":"1.0.0-next.88","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.88","@hydranium/langium":"1.0.0-next.88","@hydranium/protocol":"1.0.0-next.88","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.88_1789979892348_0.8551047138556374","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.90":{"name":"@hydranium/data-server","version":"1.0.0-next.90","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.90","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"65e7c6cf4e426d5943ee1355a1b1e79727565c41","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.90.tgz","fileCount":53,"integrity":"sha512-iMIIfgZcB+FrB9cVqO4z51hk/4jomkeQK7BB5EJOzgPy2Pnr8eKqavr5XyMOZn/zhA/w9cJuOULvP0dYrv61qA==","signatures":[{"sig":"MEQCIH5SfjZ5NARPJXJK3lpDJ6pirdHq/ZrwwyFIcNlF9HXUAiBg2cXuNGjv+Hy95mvHPA+POlkVMJAwK3dpLnfOSUwW6g==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIHmB0ErMbnRV/jE60nQAfQ21/JcQPVHmI1Txf+fsuYPUAiA3g1FGbkJuVcJHGE54R2U9RgVxnhqSdnH3Bj88bcHBog==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.90","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":274814},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"3e2ad81fee111848cc198c86e3ac6aa1c76a0ecd","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.90","@hydranium/langium":"1.0.0-next.90","@hydranium/protocol":"1.0.0-next.90","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.90","@hydranium/langium":"1.0.0-next.90","@hydranium/protocol":"1.0.0-next.90","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.90_1789986124129_0.7437090614575086","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.91":{"name":"@hydranium/data-server","version":"1.0.0-next.91","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.91","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"f493c787a5943db3e342b6d1d2eb2c5244a69168","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.91.tgz","fileCount":53,"integrity":"sha512-rLrOqJHtID7bOoshYoRzsWLmdv6JMFIDJSdn4OkRvYjYXzczAH0oZUOiOmCKf3TtrZiDVhnSpvZ1so6aStxKbA==","signatures":[{"sig":"MEUCIQDOrCdL1/xD7K0ymMPYh4QkUSbRkXWGLEZQvLrKaEdhFwIgdlFkT/SLDX1eow31pdd70Fidsp3eudCS0X+0ErkpOjM=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDLENCD+/ZhuUShMnvCNzDcXIRQI9zTgxITqFSfvjyRQQIgD3FYfunnrBRaGFfbXCQRbCh3VGAyd21R89lY8Mg+V/g=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.91","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":274814},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"4f7b482f48f14b703dc2756dddaf41498ff0e628","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.91","@hydranium/langium":"1.0.0-next.91","@hydranium/protocol":"1.0.0-next.91","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.91","@hydranium/langium":"1.0.0-next.91","@hydranium/protocol":"1.0.0-next.91","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.91_1789986790946_0.9919011541071416","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.92":{"name":"@hydranium/data-server","version":"1.0.0-next.92","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.92","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"22901addf9fb1e105106c8410ac1ddbb28bdf7e7","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.92.tgz","fileCount":53,"integrity":"sha512-2ETqsky4gP0W+fn3eQJh94TTi3rGXaxJJEtdmQp8EB7UeodAtwvL8Etvkv3GtK3ZlWxr6VnsgLVoAtER44QQ8w==","signatures":[{"sig":"MEUCIQDc3G3Njq1PZY7BQaZ87EcY7gLScQ+u5Jttsyzl3COuvwIgS9/UTLz23DLP+iWLdQGbjnHkiwCH0akxZb4RZ9kNSO0=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQDgnqkM8G9VjNdUBPY+f2+a38NwSqFe2wTfmH0lRk2/ZgIhAOcp6z/V4y0fGXPuoNsdTWSlZVtILzQ/lwDgCH4hPQHc","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.92","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":274814},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"e769e1181a2eb1e5f024f93378346fc6439ed20b","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.92","@hydranium/langium":"1.0.0-next.92","@hydranium/protocol":"1.0.0-next.92","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.92","@hydranium/langium":"1.0.0-next.92","@hydranium/protocol":"1.0.0-next.92","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.92_1789992893814_0.7549347338967656","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.93":{"name":"@hydranium/data-server","version":"1.0.0-next.93","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.93","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"79ccc070983f0c88c6a5f807ec2dc4fab4b1b098","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.93.tgz","fileCount":53,"integrity":"sha512-36i+IpU90k/stjcIkEBN22GktHl6a7h1CTQKIW1G6wdRnnBDE2bnevmLgQ10yHSn4EHCimrtM5fqGnpkCG81Eg==","signatures":[{"sig":"MEQCIDpGOyrVeyzCLNvqJ2ngIteOdyqkbqvRaKKx7IrTR7HbAiABWGvyW3tRt0Vs3VPnPOvdof9zjRy8/XAh2rvxNQ+skg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQD1G8F2q/fzJ/01BgU2UHm5TDwr8RRsWfVL2VgvL3JQegIgavw3WtoTfufdF5UOB3jILdhW1op3Lf67GADxGLvNvPo=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.93","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":274814},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"bdbb81dbc2d8d1369dffbf206d420cb67502da72","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.93","@hydranium/langium":"1.0.0-next.93","@hydranium/protocol":"1.0.0-next.93","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.93","@hydranium/langium":"1.0.0-next.93","@hydranium/protocol":"1.0.0-next.93","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.93_1789996439109_0.8414255046081676","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.94":{"name":"@hydranium/data-server","version":"1.0.0-next.94","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.94","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"6b20e7f420fbca4d5025407b65bb3dde8e490435","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.94.tgz","fileCount":53,"integrity":"sha512-sb52moApg9HpUu0GUrWYNk6yFcn7wC+zGQKi5TmBkwCNB9bT+skQxjhZHMefJ3OFTCWFSHb1334s4sYT7yXfAQ==","signatures":[{"sig":"MEQCIC6oqepkQjWTU02dOJq4YQig0xokCJnGd5qnjsArq68TAiBLM+/GmkzdmWBSypjmape3Ded70uWJdrgSWrontjBfeA==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDsdMcZTfOsSkISLE48Bu2U0EZzmeCzbSC5OG+AojvS4QIgegtFrleiLo1pqKnIegycjVVflt29kIoHSTR4W/XnxpM=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.94","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":286233},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"7e8b9eaf891f3ddea6d7c6fe4433c80d9d0b7f87","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.94","@hydranium/langium":"1.0.0-next.94","@hydranium/protocol":"1.0.0-next.94","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.94","@hydranium/langium":"1.0.0-next.94","@hydranium/protocol":"1.0.0-next.94","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.94_1789997774236_0.7348659244927811","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.95":{"name":"@hydranium/data-server","version":"1.0.0-next.95","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.95","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"711cd13e584335d3472083ec447d70efb208098a","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.95.tgz","fileCount":53,"integrity":"sha512-1iRAACgOS7sNC9Fl5JJOTGpeNnGMLi9GwfrDfpzIzDOYjbiKBjc6HX5V29hJ4Gr46KD47ZZIWvowDCgO8eCcPQ==","signatures":[{"sig":"MEQCIGalMBRbfj4AFK9iTslTI22jjWHMcwXGYXrO3cI4dLniAiAIBM+bS8BUUGlXJHQgsH0rpRHCUYRwIhJYi5TMLjkyqQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQDHbsXHAUpvcAWHV18WU3n9EiGssMPSxWu9ZaILwGddAwIhAIwh4CMyqyNDs4Cf2/22nX/wU36GzZRl6oSQb8kTL/Dh","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.95","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":286233},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"4192a93d475509f570e4130a8b4904ce62dcd5cb","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.95","@hydranium/langium":"1.0.0-next.95","@hydranium/protocol":"1.0.0-next.95","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.95","@hydranium/langium":"1.0.0-next.95","@hydranium/protocol":"1.0.0-next.95","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.95_1790001435835_0.3070196082179597","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.96":{"name":"@hydranium/data-server","version":"1.0.0-next.96","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.96","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"cffa200243ecfac0800586c69dd5ae6283bf1549","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.96.tgz","fileCount":53,"integrity":"sha512-E/H+l91aIbAyRXsEwZuH8Q8QjSuSNIyygTTbvLt5VPeCuSCTNwsodEb0Blf7P6A45L2xUz8agNiqAhsq/SUDvw==","signatures":[{"sig":"MEQCIGorZBEJjTHdUZ5ZnKbcuetrKwQlC9GitFODj4xLUUtSAiA0IRtVzI+/aoQlFz9oAz0L2FFkLGRrEm5MSNJ0ezPYnQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQCrpQixvL8H2o8Zxa7JKsJzf49U/41YAsMdIvMTmIKPZgIgV+tE5F0FTJrUOzjlIyd4+OEHurvhFyHSpiPe0CPRfD4=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.96","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":286233},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"bbaae7432df9468cb7621b2b020ceecf28802a8c","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.96","@hydranium/langium":"1.0.0-next.96","@hydranium/protocol":"1.0.0-next.96","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.96","@hydranium/langium":"1.0.0-next.96","@hydranium/protocol":"1.0.0-next.96","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.96_1790186245777_0.7755340111389408","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.97":{"name":"@hydranium/data-server","version":"1.0.0-next.97","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.97","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"2f1cee6307ba9811e6ce097772d6d22d22229cd5","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.97.tgz","fileCount":53,"integrity":"sha512-76ZDCYijyVAw0m6S1YhdvJaV8gRnmAH6lMjfh75IBPpz5ybVSafdABEfUvKTHfr4CZIpZ6nkHiXKMZ91rLC4Jg==","signatures":[{"sig":"MEQCIFCUmSJrHajpVGKkzYzyQAIGv8KNwLnVdQWm9V2GKy4fAiB1I/HrP+0/YNv79HU2MieQVcVwoFbaOTqs82xWBv6KAg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIAOsWDBofyQysgQlsZNNSURdEmnwKVXfSTqeb4lpqJWZAiEAmEuQ7zqFhN2GACIg1bCq9dpvqUnzPO0nhPELWdsmnVA=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.97","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":286233},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"140f23ddeb6416eb5e00cdc3885da83676a7c778","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.97","@hydranium/langium":"1.0.0-next.97","@hydranium/protocol":"1.0.0-next.97","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.97","@hydranium/langium":"1.0.0-next.97","@hydranium/protocol":"1.0.0-next.97","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.97_1790186598999_0.7567294217783103","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.98":{"name":"@hydranium/data-server","version":"1.0.0-next.98","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.98","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"68e30b0140a022c83eb9c3ee37a064f79a5742d3","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.98.tgz","fileCount":53,"integrity":"sha512-75i/W4wKZ0H7bS4UoOaxOUu4fVEeINrHSow0fGmOVcSWO0g/78XoQ063ElSiBeE3XCMk5wt2/5CaRvRzkqu9Ag==","signatures":[{"sig":"MEYCIQD56m9/hhxx0YWTKPsbS5e1bjCCzDEPfmiWIz9mA4Cv9gIhAKK9NqI7rMyDPWzzZEUGTC8riJYUvazX0sooum6J85Fy","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEMCHxGLyptF/Gp2fYy/+FGry8KNHw4t5L2NmUgIMtXboucCIDa4QEHI3KJqrg14i1Hq7YTWdNnmLblkDg3oOj787ik6","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.98","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":286618},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"b3e6b749d5fb8f6f44f4f242877ede97ff9b8707","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.98","@hydranium/langium":"1.0.0-next.98","@hydranium/protocol":"1.0.0-next.98","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.98","@hydranium/langium":"1.0.0-next.98","@hydranium/protocol":"1.0.0-next.98","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.98_1790187316536_0.7470382824600252","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.103":{"name":"@hydranium/data-server","version":"1.0.0-next.103","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.103","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"1d69dd9d905f58327c73af185866b48edba505a9","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.103.tgz","fileCount":53,"integrity":"sha512-E00HdB6ZPFo7mOll4aShqxbaTY1mc+VdC3MI4lsIvowCx8rGL3+XzWkd9IVUHCC5w+GTxm0OWIzAv5wTpa+8gQ==","signatures":[{"sig":"MEUCIGqnV763erY9KGVtq5yn4nP9UTUEGdn1XmMjQUHoF47eAiEAksxRIHYNCglkS7ogRnhHgC080kqrSB0a/hV4EE6/Beg=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQC1XPyJmlhGrh6LD7DKOWcEXu+DexvbFFx/xt1TjH8RxwIgDVpPFRpM3wfuqAF6SPyFYyk3zKpAimLXBAGqPU3h/uo=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.103","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290339},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"1b5fa3a4791e3d999e7b3b36db935365b78127b6","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.103","@hydranium/langium":"1.0.0-next.103","@hydranium/protocol":"1.0.0-next.103","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.103","@hydranium/langium":"1.0.0-next.103","@hydranium/protocol":"1.0.0-next.103","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.103_1790188572452_0.7481528019754855","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.104":{"name":"@hydranium/data-server","version":"1.0.0-next.104","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.104","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"2653fc08e586cf50945cdb974e146a4026440865","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.104.tgz","fileCount":53,"integrity":"sha512-qyHhp5kLQ/NMPRlJO5RF3R5uPvJ1mxzg7dzylK/xCdPxJcn5k0LMIxGSOOqtZ+J3ogZRLHfQvP9MhjwKv+7roA==","signatures":[{"sig":"MEYCIQDUmyws4e9IV1mABfRWSLSFSc8lthrRhAo2P/HWajC1QwIhAMQQ9xYrh42ffjZXupjg72m5xyzdbwlrGaf1o54KxU9q","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIFiyJsreMlokcgBtiAifUNNBKCGDw5X70FPRdjEXk6FVAiBIyDH2+HhAhZ4OZNVmHeNRi8W02N1PbwA9mArUVgcg3Q==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.104","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290339},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"cb070e687e0080403741b70131c33b6bfd2ad561","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.104","@hydranium/langium":"1.0.0-next.104","@hydranium/protocol":"1.0.0-next.104","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.104","@hydranium/langium":"1.0.0-next.104","@hydranium/protocol":"1.0.0-next.104","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.104_1790189287109_0.13427011403079425","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.105":{"name":"@hydranium/data-server","version":"1.0.0-next.105","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.105","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"cfca426dd548fb117ece5133f448e3a661ada7fd","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.105.tgz","fileCount":53,"integrity":"sha512-RfkR/GAWc3sMD5SUU1JcI8N6v7zTOpM260Aysf4TP0OuKbK2jXrQ5MxJRKwei6m26fjQ2cbpiRgGhT1FTEIEHg==","signatures":[{"sig":"MEQCICgsHQfS1k0QeUA6I5OJt6Vp8RlomZ1zG2jeRyQib9LpAiA2L7ZTUxC2aCx+ttItnh/YcSAVfq+f1XnPfPYLb+2ksw==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQCA7jUqu2C04d3qrqGITpBrPC+I7Q5eT8UwE233cMPmjwIgSsSmf/l8XARRo4fWi0F5sTCkeUbFvr6aXD9jR1ar8zw=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.105","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290339},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"1f038ff518ccc383ab0487c5d29315b803c8cff2","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.105","@hydranium/langium":"1.0.0-next.105","@hydranium/protocol":"1.0.0-next.105","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.105","@hydranium/langium":"1.0.0-next.105","@hydranium/protocol":"1.0.0-next.105","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.105_1790189722668_0.38664037778988947","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.106":{"name":"@hydranium/data-server","version":"1.0.0-next.106","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.106","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"4dad022ad9ddb0ff6bb94db9847542af13e78aa6","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.106.tgz","fileCount":53,"integrity":"sha512-q5CA1F+H1mgzSKdwVLYp22vqzXNyzRz6hQx3+peWk6DFukaTpFzSlsoBkh/m1kd7Ux2gY/g0T3f7zYZtMvPKXA==","signatures":[{"sig":"MEYCIQCGpzgbi02wfFR/JA635qF3cd4x8ZXnepcX6niTQY83rgIhAPWhqB74s8uIXiwIfznuiEl7UPlxVzKEuuNo24zOsZ8t","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIDLG4YUEl8r9ktq0DA5ePBHk4gttS+/pVdm4wtYeNH1nAiEA5q0t/djsSSWIUv4+y4lGPRxRJAzzU+7X81fq7EtOAdM=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.106","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290339},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"0b4ba0bfb1f64ffc97300019781a001d7c7c41a4","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.106","@hydranium/langium":"1.0.0-next.106","@hydranium/protocol":"1.0.0-next.106","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.106","@hydranium/langium":"1.0.0-next.106","@hydranium/protocol":"1.0.0-next.106","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.106_1790192828075_0.22455661300511198","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.107":{"name":"@hydranium/data-server","version":"1.0.0-next.107","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.107","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"816a3889b07c77bb0200c17eda3b0d8cb9f04296","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.107.tgz","fileCount":53,"integrity":"sha512-jG6cWQ2WRw566/jxDDhtZDqKbNOS71lKzYJxACmrxVX+4gX2Be3JXNZup5QXuEC6N11c0RpBwwzs8Jt0wsWUXw==","signatures":[{"sig":"MEUCIHehbJYtMj+sluT2VxjO6U5GIbFSt+GQpUjXS8XHl99eAiEAwjlTZcEcX7kcSKGd977wHG3n7XeUDUVYDCyuLvvIFNs=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIHQfOUlxlCaBJndfagBK1Mj3AMrmBBMkWoFNgnRYP+cWAiEA9KG8Sz6qOFiU7ewLXyNkVQ0JqlU3dKrRgq+LeEv+jsk=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.107","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290339},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"bb529cf424502390902ae349b301179ebb937ea8","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.107","@hydranium/langium":"1.0.0-next.107","@hydranium/protocol":"1.0.0-next.107","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.107","@hydranium/langium":"1.0.0-next.107","@hydranium/protocol":"1.0.0-next.107","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.107_1790195414377_0.21350524986420027","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.109":{"name":"@hydranium/data-server","version":"1.0.0-next.109","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.109","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"7bff35415f973dd575705feec10264ab083db5a1","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.109.tgz","fileCount":53,"integrity":"sha512-YaxLqk11SeUySh9Q+2uQwTSQmHDPzoLqTJPN96LEMmtSAWe6ESKpO/od3rMxtPH7kvFzr8OLyPUNoOEokHzcEg==","signatures":[{"sig":"MEQCIB4vEwFlala7yHs6xNGQaF0SuhjQuTOrMQncGrdnq/rqAiA0WkSXppV9yczmHe1Kdy8xoxg8/uBCkqq5yC75ae6Sbg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIDaU1AqRBVwc8cHOHWEMJHjwlfVArnp+U3PqhFZJWuwuAiEAqOENzqmNf8YkraM5PMhrOGBj9ZsDOaEVzkmgoEX42EA=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.109","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290339},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"137baafcb95589fab3a54a6645803d387b81e8a0","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.109","@hydranium/langium":"1.0.0-next.109","@hydranium/protocol":"1.0.0-next.109","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.109","@hydranium/langium":"1.0.0-next.109","@hydranium/protocol":"1.0.0-next.109","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.109_1790204417207_0.1855916468498351","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.111":{"name":"@hydranium/data-server","version":"1.0.0-next.111","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.111","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"c3cef318dcec27b26122acfc134082d0ace37dc6","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.111.tgz","fileCount":53,"integrity":"sha512-nmphrjFaWTTXT1fI7O/LLBm+LtcqDTOaw5+5Ubua+qsNxrZIkz+c8i/D3UE6igrxTY1ANbm73BZPUwm65O619A==","signatures":[{"sig":"MEQCIANGJrzBT/bXErhwslMNZphUNoHjpEJ+3fSox8i2d/vLAiB5R4xZ/KJiGdRNQRSn0GnnkwcV9526bN/vwPeYTBCyzQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIFnV2Ly2Z+s+JgQYeK2epEZMppBeu+uI2e+lgGN+DbL5AiAIQfjBCS44vQ5ha2LLLlpTCb5Fa5ExwPAoE45yP6rFcA==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.111","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290339},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"8add1d2ad3dbaeeff870b21f3bcf13361a37e28b","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.111","@hydranium/langium":"1.0.0-next.111","@hydranium/protocol":"1.0.0-next.111","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.111","@hydranium/langium":"1.0.0-next.111","@hydranium/protocol":"1.0.0-next.111","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.111_1790256590434_0.31869605158293246","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.112":{"name":"@hydranium/data-server","version":"1.0.0-next.112","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.112","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"647eaa09abf06dfc6d3d5d5d30301c1e1dff5550","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.112.tgz","fileCount":53,"integrity":"sha512-D8kXcHSv4GTsx30c3RKDqzO0n7PB90elhKTnGfzLoonjmjP3ERXsTptGFXxbCmFtzeSj/C+flGhGmsJSG+E+Qw==","signatures":[{"sig":"MEYCIQC0XxIimfEHWYXcNvJRrojQMCKr91cK6NvIDpFacTz/bwIhAMxPSv8lQ2M7rUwzE3PMUhic5x2AmV7VR8C9qUofOKQX","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDAN3Fg1W7EHuCEcMcL9GaJjD5x+FxttEiNgbwGR98emQIgbM0GRfq3/t0ZWQSleTfJhJ05QKyiWWec/0LlOOAns3A=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.112","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290251},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"f1f9ddb7e3bd21283dd982005add36ac4ad39859","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.112","@hydranium/langium":"1.0.0-next.112","@hydranium/protocol":"1.0.0-next.112","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.112","@hydranium/langium":"1.0.0-next.112","@hydranium/protocol":"1.0.0-next.112","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.112_1790260390990_0.6793671474880707","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.113":{"name":"@hydranium/data-server","version":"1.0.0-next.113","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.113","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"e67f95ccde30d345d28a9203ce58f5acd8b31f37","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.113.tgz","fileCount":53,"integrity":"sha512-Sd7+qi/w3/UtC30ukkGTLYiCsWnTnvEL3gRKswFk4dVTfNYqvaYmrzHh3sCEw50gNHsjs5e8uIa09HGM2KkVbw==","signatures":[{"sig":"MEUCIBvBSHxwvhskAnYLWKlh8QOU08m+mTehwl8Rerz0jJyvAiEA9J/5wdYdp53/BTjiqFZPMQsoyAAuPnJb9VDZv8sSZyA=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIFZURYG+PnWsJd0fXu3/lbwJE0fVxy4J82C8HrQYijKBAiEAk04eG0Aa8wyleNG3H6eXj3J+xMnmWzLbc7L2ZRrsuXw=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.113","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290251},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"c27a580af54cc7f72ea5f6363e3af6b86adb08f2","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.113","@hydranium/langium":"1.0.0-next.113","@hydranium/protocol":"1.0.0-next.113","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.113","@hydranium/langium":"1.0.0-next.113","@hydranium/protocol":"1.0.0-next.113","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.113_1790264305614_0.6677240090184902","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.114":{"name":"@hydranium/data-server","version":"1.0.0-next.114","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.114","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"266c3f0dd71998bcc4d0622afae24008d26015ca","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.114.tgz","fileCount":53,"integrity":"sha512-4ZIuUgQSSkjhpZym3Lt46+FBNig4/5smHceAJFXn5jvQ2XzodmB+trZgO1K/njzEY+vCq3r9WKJl6fAMXBkBRA==","signatures":[{"sig":"MEUCID65lfYY54G2okJNlUxmcYXHc6ZAt69mc8Jx0CGAoBqiAiEAoN8GBIFaycpaoO+0toBtmKx3vwZxAX1sD/tk136hObk=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIHbeHRUpXR46/TMpVmFpYZW5173X6EUYWuCgqMZrOoatAiAbcth3N4n1OGPzBMEvA8JhXlHa0vMsSrbBu2JFMUzXfQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.114","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290465},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"212f8bb8490512f4e60a1f153659efeb7b399d53","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.114","@hydranium/langium":"1.0.0-next.114","@hydranium/protocol":"1.0.0-next.114","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.114","@hydranium/langium":"1.0.0-next.114","@hydranium/protocol":"1.0.0-next.114","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.114_1790268315347_0.40797436884684024","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.115":{"name":"@hydranium/data-server","version":"1.0.0-next.115","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.115","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"22edf919126e4d944a70d931a7c56ec7839f089e","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.115.tgz","fileCount":53,"integrity":"sha512-X4gD/N0HZR6WHkdCA3xVTC8jlVz8OEdbuz9RjUJIqgv92x71Sw7Td0eA0pDY1Rm0pMEMjo/wM5MKF+ZujvL+uQ==","signatures":[{"sig":"MEUCIQDF2URrKPhwlpufISLJ4NUCC1p2yKbhiBP/TH1Mzu4wjgIgL6LT6zXnlqiBzyYoFwugcNCG40jEv2uYGUV0N5KOxy4=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIHNxc+3M1YVJ5cQw6teUHr+htWELHOLDhdwqINfbAnTLAiEApCOppYNoO1T7Dyka8/2M9DaCepKXKVRpvwXOsHPSu7A=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.115","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290465},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"eeaf6fbeb80edb859679b15b636e83233e989b9e","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.115","@hydranium/langium":"1.0.0-next.115","@hydranium/protocol":"1.0.0-next.115","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.115","@hydranium/langium":"1.0.0-next.115","@hydranium/protocol":"1.0.0-next.115","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.115_1790286279665_0.7606305352406955","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.117":{"name":"@hydranium/data-server","version":"1.0.0-next.117","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.117","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"ed4d660c9a2049220bec4fe16d354195ec09c029","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.117.tgz","fileCount":53,"integrity":"sha512-f41Pe9Iq9Y5NCX9PewvSOBCnuQzlBW9hJW05tFw0qeMdATjiMtM03fea4J6GLGztD6R7aGqjHAAVtDh97GBhrg==","signatures":[{"sig":"MEQCIA1ud2se4mb8MVJdDCvKyYlJ8/lkpBJYNPQ8igUTH2/rAiBerCMmjg5pH2oY5Bgwm9Y44tAi16dzE8xih/kJCGgJNw==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQDppG4XG/Hseoi2i4L1ZA3yjx8sz7+9lD3Y0+4DF6oVIAIhAM1ocD9MIh1qJKmOq/tLieSNTc/lDnkA7pjUxpmZnwpV","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.117","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":290465},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"45a1a35a68595f731aac6bd16d109d3226827521","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.117","@hydranium/langium":"1.0.0-next.117","@hydranium/protocol":"1.0.0-next.117","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.117","@hydranium/langium":"1.0.0-next.117","@hydranium/protocol":"1.0.0-next.117","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.117_1790631856049_0.6245413105542676","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.123":{"name":"@hydranium/data-server","version":"1.0.0-next.123","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.123","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"29556cf3981e43d031c4b83cb096f42ec33c1daf","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.123.tgz","fileCount":53,"integrity":"sha512-4ZGNmrXxakGrTw7Gd7YcJ4B7y1sEHxZVsUKzY0xRv1+O3kL5NwQfJTZhxtuEYJECklP0UYeIaPFUnZrCfiEbgA==","signatures":[{"sig":"MEUCIQCii8wIVALoYRHOvu+xdY3kcLdaftqXq7MuQrLnhDd7CwIgHNcNIXiY3+jBW3EGrZAP/jBYKvYtV6C33xgUCRPQLOA=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDCcNOBdOaLIW8DzAWKQR2DJg940s2Gt4o3W62aAbSWrAIgVjMM2+3G2SX5WMzW/aDPycGi/Dt1dc1SZtXcX4qCQhI=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.123","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":302101},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"6b7cd61eba0925df8150ed0a438804dc43c24319","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.123","@hydranium/langium":"1.0.0-next.123","@hydranium/protocol":"1.0.0-next.123","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.123","@hydranium/langium":"1.0.0-next.123","@hydranium/protocol":"1.0.0-next.123","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.123_1790633243955_0.33420406312862405","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.127":{"name":"@hydranium/data-server","version":"1.0.0-next.127","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.127","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"e8822dd1a0ddda9253fb2ed8703b66da2707e32a","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.127.tgz","fileCount":53,"integrity":"sha512-Hvi7EIIoa4L1k6/n7GfsRj+VbjHhYaBb2VLg0mQGpE4hh+bsBfZIZDSCAPIxqJXyC98/yTOQn5FjZmvEgXHnYg==","signatures":[{"sig":"MEYCIQDCTHJYfWg/uxColRn3xvEw9gUB09K2ahYDQk0udx20WAIhAKPtBgm8pqVsHB4imzGUkPf4w2+r+OF3PTQNhYVHgOIt","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIFzTRHIfDx7P/SzhwEd4G/tEDeneUSlloBLztD0/pGB7AiAga5VkHyL81GwaKsGn3M2hKka1su8zdaQyYLIbOl04kA==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.127","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":307290},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"11cf902498b55aea98fb0c9fd0cc8788c7518539","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.127","@hydranium/langium":"1.0.0-next.127","@hydranium/protocol":"1.0.0-next.127","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.127","@hydranium/langium":"1.0.0-next.127","@hydranium/protocol":"1.0.0-next.127","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.127_1790634921406_0.13806545256689584","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.132":{"name":"@hydranium/data-server","version":"1.0.0-next.132","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.132","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"4e8a8bb69033dd75273e71b76d15c16ebc17bfcc","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.132.tgz","fileCount":53,"integrity":"sha512-4az4InuOiyaJZLXSvc2MsNLJmXY3J4XKtg0xfxL0udxz7htE131Wl+0pmhFTFD5tfDWRmWWra0ySxNNY91XfIA==","signatures":[{"sig":"MEYCIQDp8jSlEz4GnOuuvhSOU0Fee2LlM6zK8/a9ZZ4W4W3rXQIhAL/aJq3RlMjKWIxoNwVaBLxqMhfvIiMDCtLe+9kQIGmR","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIE+XP5EhGW4WtP0Eu14LgoPyP7dpy7XTcTtATVJgGtFiAiBIC9DWD8+6zrr84Xgqao/3+/sKwye32SZdJnaILLDXYA==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.132","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":305979},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"27dbc2470c7b60e0097425e4c4df6922ad9a22bb","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.132","@hydranium/langium":"1.0.0-next.132","@hydranium/protocol":"1.0.0-next.132","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.132","@hydranium/langium":"1.0.0-next.132","@hydranium/protocol":"1.0.0-next.132","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.132_1790635689356_0.11496915861146806","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.135":{"name":"@hydranium/data-server","version":"1.0.0-next.135","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.135","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"a3b5920d3965f067d339647e7b2b2f74e3080db2","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.135.tgz","fileCount":53,"integrity":"sha512-1EqmeFw6m9l1iksXnWGaImZPpjyDo/44+HOracMcqrxklnBZM6HnLXxHaJ1OaqF7kt5XrFLiTrWrSfeRwYNNRQ==","signatures":[{"sig":"MEYCIQCQgcN6pqCMkxXw7fcFoRzZWZvUB2JC+kEhC+bIyz9xdAIhAP9vJK95rMomkSa+YwbVBgUx5wwle/Ccjt8Y/PzJOLn8","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCID7bods+tE8J66wf+qjZUzC8Yhq6YIheZpdgTS3ifgyZAiArPZL/9dyFZvcvmUJ+WYHf0e7s77A5741vNPcN/L3pgQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.135","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":307408},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"cf87c80702f9ec9b1c58bc1f3499cc87a8bd3ef4","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.135","@hydranium/langium":"1.0.0-next.135","@hydranium/protocol":"1.0.0-next.135","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.135","@hydranium/langium":"1.0.0-next.135","@hydranium/protocol":"1.0.0-next.135","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.135_1790636315476_0.7673866825890869","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.140":{"name":"@hydranium/data-server","version":"1.0.0-next.140","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.140","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"5f8d4b7d0c11f556d30179bef179b2f01cf8518f","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.140.tgz","fileCount":53,"integrity":"sha512-AgORtq2XC7tWcZYO6bJw0vMJ1Je6e7C8vutEU4OL7z4pla/HfIkLpi2Y0yCnIlMx/cXRN8SmyCGuIV+db+v28g==","signatures":[{"sig":"MEUCID1stt8Tb1NgsJTNrF51+UZfmcOzm8sw7/iOgBxeKLK0AiEA3slUXCBpbWqNUUsETh8EPhrekV5zZb2toP0TWVjQYMk=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCICscgqqk+KLKPVIINP1ndPx5BMywLMfzAP66IzdnCm2mAiBHNLF4mswxZtdyhaYlPtTR5c3NPg1qujfuv/RPiSpipw==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.140","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":301654},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"427719cb511b0dcc901e7813ba7fde37573c6a7a","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.140","@hydranium/langium":"1.0.0-next.140","@hydranium/protocol":"1.0.0-next.140","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.140","@hydranium/langium":"1.0.0-next.140","@hydranium/protocol":"1.0.0-next.140","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.140_1790636614237_0.31998255463947767","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.148":{"name":"@hydranium/data-server","version":"1.0.0-next.148","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.148","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"2e05de00042c8d12bc0a36a4026f87b6ece746dd","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.148.tgz","fileCount":53,"integrity":"sha512-yWXVeIcTBaiSAzB08hJMxgsgTGn6GemwlqQClKtV73NifeInG+J27ukW0yBf+t4cVUleEaAkmrjVElmcYg8QlA==","signatures":[{"sig":"MEUCIAypgg/WBB+VWJOOnDLFEImGWtw1tY+Pa7W9Waooy9tkAiEAuZ8ZKe4qG1lJqzACXciL+UwnD8XwsLL4cIL7EAdc3bw=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQDUhWxGmEyDk+JlNQCiw/cQO2Eb1XnWh6RIRhJ0hog9KAIgeWmU3qashfCy8GRRGe7Thpq1ztaqupGUPvDeAos2YkY=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.148","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":301157},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"9a0f51ac8c2a36bf898655aec9bc3abff8bab721","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.148","@hydranium/langium":"1.0.0-next.148","@hydranium/protocol":"1.0.0-next.148","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.148","@hydranium/langium":"1.0.0-next.148","@hydranium/protocol":"1.0.0-next.148","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.148_1790637486408_0.4801982667745861","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.155":{"name":"@hydranium/data-server","version":"1.0.0-next.155","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.155","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"4678eeaddbbbd3a44925bb6ea580db742c8289e7","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.155.tgz","fileCount":53,"integrity":"sha512-i+gwgmYPx1VvS+xbsCAEujizd+nOCwDIk04NjmjZUXiCjqGTKoFiVCMTod81z/Is1uinlh5fIGwJOyG7rrp/XQ==","signatures":[{"sig":"MEUCICxHc+0oUOHhStOJIjjYny3mY2TXT01cg2UE2y8iKPobAiEAnY/oi9UtXKJuMgyXXEaowydv+olVWDxhi4oDF3TaDkw=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIEuS1IP5peq5GiVnC5O4r9lf7OjCjc6q/ID6oYwGrpkMAiEAqrb9z2IJBS7uVXkcQQKDvyPBYDFc34alCsh+OiRUKUc=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.155","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":303755},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"2cb4a686814289a2d90c73f977358bd4c43f39b3","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.155","@hydranium/langium":"1.0.0-next.155","@hydranium/protocol":"1.0.0-next.155","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.155","@hydranium/langium":"1.0.0-next.155","@hydranium/protocol":"1.0.0-next.155","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.155_1790638683077_0.25106128203261346","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.157":{"name":"@hydranium/data-server","version":"1.0.0-next.157","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.157","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"c73e97b36be46d43cde387424491383e7d571154","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.157.tgz","fileCount":53,"integrity":"sha512-FlN+lUTlhTdaF+P5aSC3tSEliNwbPN9lSFslLd06eFSmbUm/3MI4/5tKwWMfsGGU9cbbGGkDyYBLOMKKibgeYw==","signatures":[{"sig":"MEYCIQCy0qqDwhCandIlrhsZQO41a+x7jl/RWG21uf/cDa8LnQIhAL719f7osxmBqTzFQGO5BsoCMcITZF+TIGgiQCv47hfl","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCrTGEkhbO9d7JkVMg3dr0AfG1KLQmD1sZ6hVvAnfOyZwIhAL4m4dCdRXKHadAGqjnRI29Gg41Cx4Xslf23XgpzhjoY","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.157","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304493},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"eae73ff47f93d344488d34b082f92732c93ad31c","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.157","@hydranium/langium":"1.0.0-next.157","@hydranium/protocol":"1.0.0-next.157","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.157","@hydranium/langium":"1.0.0-next.157","@hydranium/protocol":"1.0.0-next.157","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.157_1790639351377_0.36221758853037467","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.158":{"name":"@hydranium/data-server","version":"1.0.0-next.158","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.158","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"fb5abc8e95319c020c675db9b71fa4f2b751e0cb","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.158.tgz","fileCount":53,"integrity":"sha512-B+xe7txn2s0fFLU/zlK4K4LgIa0lQogx+DLe1BZyA/Y/j1FJ/kULVEQKncqqrmfVvWKdAEtczMKBk+5ZwN9uqg==","signatures":[{"sig":"MEUCIAe83aerQNLfpHchF4dgPRqtYW5wWQUlBXTy3TZWvEzQAiEA2OjoGKHjROfDtukyHXbGTiD0I/UmJhoUJbHE5iDp9lA=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQCpJXmZ2+I5w7oW3bnTKu29iyXKZ2QrnIVxruudeJeoYQIgFVfo2d5RTkXYnGoE8W65LGr5QqbboQKJrAMnjZSt1E8=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.158","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304493},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"1ee20631bc2bc0164de8f4b0fec71bbf78b0a9c2","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.158","@hydranium/langium":"1.0.0-next.158","@hydranium/protocol":"1.0.0-next.158","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.158","@hydranium/langium":"1.0.0-next.158","@hydranium/protocol":"1.0.0-next.158","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.158_1790757993226_0.09854361910144549","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.160":{"name":"@hydranium/data-server","version":"1.0.0-next.160","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.160","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"bd58e4654af45374e045754d9af7deee220e5f8c","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.160.tgz","fileCount":53,"integrity":"sha512-wKry8/6CGs2150ps+UpvMr/Ze5Y7VrmKNu832jT3QYI8Tp8LZX7tuwR+hgXbmIonplsgO4M9VNNsujNNwG2p8g==","signatures":[{"sig":"MEUCIQDHzI+a0n1Oh2Z4R067IpTxQ1svDSRVSOU5RQSAq0xqmgIgJiAF/xC+ntL/ELC4eBotwzFCJY87+zd+7EcFVo4RdL0=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIHfVb3HuDefd8pQytsNnc7MKZSXcd5mVWx4gjoe+QSQTAiBpAP9o8/A+kp6nskFgwdtVf0dJ6EpsLeUy/h9IwAeLxQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.160","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304493},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"6cd23686acadcaf2dbb4ea757efb4ce32bacf77d","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.160","@hydranium/langium":"1.0.0-next.160","@hydranium/protocol":"1.0.0-next.160","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.160","@hydranium/langium":"1.0.0-next.160","@hydranium/protocol":"1.0.0-next.160","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.160_1790762584923_0.736292944753383","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.168":{"name":"@hydranium/data-server","version":"1.0.0-next.168","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.168","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"1e87523e1f6dce15b07bcb062153ab88eaf7d3f6","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.168.tgz","fileCount":53,"integrity":"sha512-Z2lNZXaLY5rlUExu+FCgO+KllMSyqNQaC/rb17nHdGqF6lhGP1OR0N+oCIS2RROw1igd0nDJZFaVA7xxaivPDg==","signatures":[{"sig":"MEQCIDKsnKvBhu0aRT1nXWV7nHDn2uFPpN8myi7C2KHv0nDVAiB+ct6gQsq8LuB5bRuKbSTVQHLhA2gHJNdPnn7kW/SQ9A==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQCxX/kWv3oGmc6wZL7/VBg37QKTRH/iGc6M7jIO6/f7PwIgRJIcv+wV75Icq2iKw4i34CTK9QemjHS8FLscUEpp4tw=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.168","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304493},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"30b7b26e0bb67f2a7b372b5a62e83d45905d8663","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.168","@hydranium/langium":"1.0.0-next.168","@hydranium/protocol":"1.0.0-next.168","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.168","@hydranium/langium":"1.0.0-next.168","@hydranium/protocol":"1.0.0-next.168","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.168_1790777226634_0.771667440471095","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.169":{"name":"@hydranium/data-server","version":"1.0.0-next.169","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.169","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"7357d4d210a443a992da44216994596bb96c1f80","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.169.tgz","fileCount":53,"integrity":"sha512-FWtxFck3cLqWqynv2tb1/kmcR7khzZmESj2/D7QS/BOOYFNlOxh8fxDsyNxTSQP6rfZzzqVam5Q9oulEF+tq/g==","signatures":[{"sig":"MEYCIQCQpgfmMk96Pc68Zt/V8pmGklp86xcr3qLDIuD0DrYrnwIhALbfjIq0VBkXGFnPLAeS5Em/zVrbP8GUIG3g2TgwQD7+","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQCcYfB9mq1Ny2rBGJepgsgp0JHIFqYK/0KRMOR/QJGI5QIgSl29e/Vaj++GJdz7qLCRD9Vz9zAZd568SZaw7fqQJqQ=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.169","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304493},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"0a17cbf5e6bf32df0827e51ffbd602b4e722bf2c","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.169","@hydranium/langium":"1.0.0-next.169","@hydranium/protocol":"1.0.0-next.169","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.169","@hydranium/langium":"1.0.0-next.169","@hydranium/protocol":"1.0.0-next.169","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.169_1790783232703_0.24021860287986363","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.173":{"name":"@hydranium/data-server","version":"1.0.0-next.173","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.173","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"f04f891c8d1c72260654cd7844b6dc1a7c247912","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.173.tgz","fileCount":53,"integrity":"sha512-XxUgu7rAMqK1qsTgq4y0X8Eyqz52si6JjcqwjZZMqI13E+nJ5IQ90RwKfYe03/9O4oQ7EBWRq7EfXG0YVaJ8IA==","signatures":[{"sig":"MEQCID2xaxFJqPn7EslXOCmdoos6CfYEAnWw4EJ8rrlrgtdXAiAsdipPh98/m6n4KClLoWZSOtE9OsweXGLHeEtXww5f9Q==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIAkqihYIZ1ScvAiAFNqYqnS17asSqQan+l3YZLCoVkvCAiEAyXr/OM63tqedL7/oh5nHBx5rvnx/O/pQqxe7ZVimXHw=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.173","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304493},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"5bc225d4a40a2de4e9b175721db25ddb7e48c348","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.173","@hydranium/langium":"1.0.0-next.173","@hydranium/protocol":"1.0.0-next.173","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.173","@hydranium/langium":"1.0.0-next.173","@hydranium/protocol":"1.0.0-next.173","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.173_1790860453934_0.5324917327426679","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.174":{"name":"@hydranium/data-server","version":"1.0.0-next.174","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.174","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"5feaed3f19f9830d7ff279e288b52599bc4577d4","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.174.tgz","fileCount":53,"integrity":"sha512-hm9I1+zieycZAgbagDfzmVTHeROcdhfcQem5SB6cddSQWC1gpm8pqaNhm9VTRmrps8wgl252oqcKxu+d6P4IVA==","signatures":[{"sig":"MEQCICsuCZb5hIZvmqDpp4L3YlHRVajJbS5nZM4PZwFFSzDsAiATZZhNecjxo9QxTFHENxj0M2QgDA/D4xIFB+NO/VstAA==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIE6cmDRMSE2thyjO8FXrjyyClkSSVfr/9x1iUYjsoTumAiEAmvHpsdItK1k99ZSHSpgYHx96i0DsiDmG9ywyDtjQchc=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.174","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304493},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"58cc70efba83953130a58afc689770123cd9a73f","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.174","@hydranium/langium":"1.0.0-next.174","@hydranium/protocol":"1.0.0-next.174","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.174","@hydranium/langium":"1.0.0-next.174","@hydranium/protocol":"1.0.0-next.174","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.174_1790926715942_0.7212140954215334","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.175":{"name":"@hydranium/data-server","version":"1.0.0-next.175","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.175","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"5788c5b8e5c4724a9662a4f17a1a22b18366b109","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.175.tgz","fileCount":53,"integrity":"sha512-+aIB9dE4qMG8t5hgSF3+NJ0VO0o0EoTbDbEKepvK3Iv5bKsxLFsTJ9icaX/WurjOi4FdPvR1bO5VqyIB8o0DWA==","signatures":[{"sig":"MEQCIDsMmEGbtOR7/cbbUc+JHvyIExX7nf951v5ZxBRWMMLTAiARAu2SSeEAfhjVz3ej87v6rfJWvLYv1eT56cprJGc3lQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQCUu9hLpOSB71/vWzmstIiIqWi5jmGnLj8OKmykqpOtIQIgbQwyAJank1ZmCcTntaUrtIwZ+Uq/4QjB42j9tVcgY5A=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.175","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304493},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"55d99da61a0fbe06d1225d170854d5d7ed7beb4c","scripts":{"lint":"eslint src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.175","@hydranium/langium":"1.0.0-next.175","@hydranium/protocol":"1.0.0-next.175","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.175","@hydranium/langium":"1.0.0-next.175","@hydranium/protocol":"1.0.0-next.175","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.175_1790927480715_0.5833804920383756","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.176":{"name":"@hydranium/data-server","version":"1.0.0-next.176","keywords":["hydranium","langium","language-server","lsp","rpc","data-server"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.176","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"f585867de61b23b05ef2f82dff35ecf0a6912c2d","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.176.tgz","fileCount":53,"integrity":"sha512-OgLo42jQmniJYshk1IE03WJnURJvUBtYivFQgtXJHIts7dneMITRG9nTmw29QTRACwAJz37cpGUDTQLwg0VOaA==","signatures":[{"sig":"MEYCIQDD7UGYAeiSjo85R4VXPj7k/yGViQWxsgh3OZE/sBUoEAIhAL4AVLC1lo9IHLZBtcpI7v2AZD4wWeyxbnbE4/oGJ+Pq","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCIQD0FGxRZORUxBCDmQl4gEdjD797sfTNshz5j+td2/XRtwIgHy26LsdZlOHA2QbJq0spsM0MozZ0aIAIYvXAPe5Ezn8=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.176","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304543},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"f2701eb5d00f38595d2099980346074d70ce4ee8","scripts":{"lint":"oxlint --format stylish --config ../../oxlint.config.cjs src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.176","@hydranium/langium":"1.0.0-next.176","@hydranium/protocol":"1.0.0-next.176","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.176","@hydranium/langium":"1.0.0-next.176","@hydranium/protocol":"1.0.0-next.176","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.176_1790935440772_0.6811887288570271","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.177":{"name":"@hydranium/data-server","version":"1.0.0-next.177","keywords":["data-server","hydranium","langium","language-server","lsp","rpc"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.177","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"342eda9759db04ccaaf6c77a9c1a9bc19f7768be","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.177.tgz","fileCount":53,"integrity":"sha512-0gEwdfkiJtDmxdWoXcFy+v+CCOKn0NpSbpcNO91A01X/5CzaQDV8dOB0McFjSMe5rUbF88CDZfQ1VVPr8rMOCQ==","signatures":[{"sig":"MEYCIQCjEhov5lGr2WDDpHJ6Edfb8HtBCI8AaEQnKABZi7gm1AIhANKq4NTaG8aYEDGtDqZyoxff4Xw8zGmo/g200q+9FGv5","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIDZLvVi6b3dSf4fLH66UXCJY4XCrsGFHpP8eS4wISZ3SAiA7/KOAs/RGrGj5mHcrzL54H5dH2V2u7wHW3gmwxHKoqg==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.177","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304543},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"0bd2ddad64f34cf251c80077f0755b69eae738b9","scripts":{"lint":"oxlint --format stylish --config ../../oxlint.config.cjs src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^5.8.0","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.177","@hydranium/langium":"1.0.0-next.177","@hydranium/protocol":"1.0.0-next.177","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.177","@hydranium/langium":"1.0.0-next.177","@hydranium/protocol":"1.0.0-next.177","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.177_1790940519956_0.5216871237308878","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.179":{"name":"@hydranium/data-server","version":"1.0.0-next.179","keywords":["data-server","hydranium","langium","language-server","lsp","rpc"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.179","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"9e2a2c2862dd52a1f0ed4a40733627790470bf5f","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.179.tgz","fileCount":53,"integrity":"sha512-fedlFWaa4csKal8474tjrwgeHzeehVkMLm5lflmx/Og4bQlkAeUpENdwdE6t+muB9p83fsyVJS0zf6wVmCq0bw==","signatures":[{"sig":"MEUCIDkCOZFq/ZdO6HGgtMC9lYP2/Ij7qnMzvAgrMvQkaAfLAiEA2yBDUJVYxJzKFUiN4as4Bnykhtmk9NFmIBAEPFK7oG8=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIHV+oEUhzgnSxOKfdQYttKcLw/l1WUpzMFU7ZC8Aq9pjAiBgXyFxTzv0x7WLgRFiN5rTa66n/3nzvJiRfN3HEs8IoQ==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.179","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304823},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"d98696eba7798a8392b601d15a66884764e59d9d","scripts":{"lint":"oxlint --format stylish --config ../../oxlint.config.cjs src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^7.0.2","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.179","@hydranium/langium":"1.0.0-next.179","@hydranium/protocol":"1.0.0-next.179","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.179","@hydranium/langium":"1.0.0-next.179","@hydranium/protocol":"1.0.0-next.179","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.179_1790943413103_0.5362832483878968","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.180":{"name":"@hydranium/data-server","version":"1.0.0-next.180","keywords":["data-server","hydranium","langium","language-server","lsp","rpc"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.180","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"08434060f64ba0dc73514ccb93f1a0cf8d018eaf","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.180.tgz","fileCount":53,"integrity":"sha512-rzjM2tSpVhY6buyrpVMAl0ZAXLnnsICygokfm3bMMlZi2rSugThgHnYWt7O5jFA5dgPoXRS7NtGGFkcLOkmp3Q==","signatures":[{"sig":"MEYCIQC6T7UDyPmN47xup2+i9kSBg9lcyVkAr3FnKslq5qG39QIhAO9ODPtx4/VtZqBOj7JyVzS3OeBJc9TIiqx1KaEgRB4a","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEUCICskqmK2fyAhjxXGOOJO3cO8GpvNDBGXo1y0CzByLsMIAiEA0WmySjmhzq56kQF46mLuglQDbnajacy9qzWTgtNenAc=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.180","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304823},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"c9ca6f89b51f3cc93e1316bda7710f30c130187f","scripts":{"lint":"oxlint --format stylish --config ../../oxlint.config.cjs src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^7.0.2","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.180","@hydranium/langium":"1.0.0-next.180","@hydranium/protocol":"1.0.0-next.180","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.180","@hydranium/langium":"1.0.0-next.180","@hydranium/protocol":"1.0.0-next.180","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.180_1790944931580_0.4690945329352836","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.181":{"name":"@hydranium/data-server","version":"1.0.0-next.181","keywords":["data-server","hydranium","langium","language-server","lsp","rpc"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.181","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"3b0c85cef61c38e67cc4a6372dec8718cd37f3c2","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.181.tgz","fileCount":53,"integrity":"sha512-O2jzYRJebaC9IE2NzvtWby6CXzgeqzflyXFxyrmAZq/jiRI3+MMZsGJG/WFsB1cb15pC5zVadtyGaw9sFvpgwQ==","signatures":[{"sig":"MEUCIDfPyAGsPe8gdQvtCDdb1RLLcaJomVv0ELV/0luQONr8AiEAuoqDAjTYS3JkkOFVwBJPwJiM9619UBRcZyhm9SMme0U=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEQCIHntR4CxqMOidwXVtgCjYVVXdexPuIngTRSFQ/JWomVzAiAk/bjmNOLv9u4NF3fb+pNni/1CDPBxSbL741fM+8sp9A==","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.181","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304823},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"2c50797f9ce8e785cd1f2269e6273bb4f6425662","scripts":{"lint":"oxlint --format stylish --config ../../oxlint.config.cjs src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.13.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^7.0.2","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.181","@hydranium/langium":"1.0.0-next.181","@hydranium/protocol":"1.0.0-next.181","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.181","@hydranium/langium":"1.0.0-next.181","@hydranium/protocol":"1.0.0-next.181","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.181_1790945558464_0.620637785646206","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.183":{"name":"@hydranium/data-server","version":"1.0.0-next.183","keywords":["data-server","hydranium","langium","language-server","lsp","rpc"],"author":{"name":"Hydranium Team"},"license":"MIT","_id":"@hydranium/data-server@1.0.0-next.183","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"3b5267b25d85fb1ecd1c65e2e44c091043ea3ace","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.183.tgz","fileCount":53,"integrity":"sha512-lyXLQAxMlhLxzNKqasZB8o60wyAhn2vvuGvnGWxRlThK2rZ9mNwbocfhJPM/94IdSlhJDDhZ6DHs2f1A2rLV1Q==","signatures":[{"sig":"MEUCIQCg7Geh/HeZl0dESyErDudK8t5BRRJgf6nFb0cN76wdmQIgNnnvT32nXTfyubHuPlGVm5sxwZGan/lbeMOHw0ShMqw=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"sig":"MEYCIQCpVDXSP1KGRSz/9rU+Ao4o4Mh6e5LpKrGOcP8zkcpeEQIhAMbZRn8zTqovChMH44VklFsvxGWw/4SXs6gQ2c6Tu5PM","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.183","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304823},"main":"lib/index.js","type":"module","types":"lib/index.d.ts","browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"fe055eb63801c1e2f1943b55ff7821f2774b9ff7","scripts":{"lint":"oxlint --format stylish --config ../../oxlint.config.cjs src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"sideEffects":false,"_nodeVersion":"22.18.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^7.0.2","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.183","@hydranium/langium":"1.0.0-next.183","@hydranium/protocol":"1.0.0-next.183","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.183","@hydranium/langium":"1.0.0-next.183","@hydranium/protocol":"1.0.0-next.183","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"tmp":"tmp/data-server_1.0.0-next.183_1790947674175_0.29896178637475757","host":"s3://npm-registry-packages-npm-production"}},"1.0.0-next.185":{"_id":"@hydranium/data-server@1.0.0-next.185","bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"dist":{"shasum":"230b99b11da6db59d837991c55a7eb842a96e098","tarball":"https://registry.npmjs.org/@hydranium/data-server/-/data-server-1.0.0-next.185.tgz","fileCount":53,"integrity":"sha512-ftvGqy+lz0FR60OuUle8TU2alBJJXnQ0R/Rqzo8MGzNwrHCjQdllFSeOZyfhTJ4o1nEEH9NrhFhXR2eTTFpeNw==","signatures":[{"sig":"MEYCIQDMnEZ/vh1mCZEHzK3Q6yF5e+LCxBLFe1GpMwmyPIC3lgIhAM9UVw0eSB90mhYPbHub7pCKRoKkOuMICL6iusXQnnVR","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"},{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEYCIQDQ8q8vW9qQ4d22LAzvaR7fYslMa/4qjGpbgJgj8otf4QIhALWmpTTd8rbi/s81BfNe8EwViZFe39tc1mSwqlijwYZQ"}],"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@hydranium%2fdata-server@1.0.0-next.185","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"unpackedSize":304823},"main":"lib/index.js","name":"@hydranium/data-server","type":"module","types":"lib/index.d.ts","author":{"name":"Hydranium Team"},"browser":{"./lib/default-diagnostics.js":"./lib/default-diagnostics.browser.js"},"engines":{"node":">=22.13"},"exports":{".":{"types":"./lib/index.d.ts","default":"./lib/index.js"},"./node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/node":{"types":"./lib/node/index.d.ts","default":"./lib/node/index.js"},"./messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"},"./lib/testing":{"types":"./lib/testing/index.d.ts","default":"./lib/testing/index.js"},"./lib/messages":{"types":"./lib/messages/index.d.ts","default":"./lib/messages/index.js"}},"gitHead":"0c1f5de214bdd827a96cf271263260f8fb9759d3","license":"MIT","scripts":{"lint":"oxlint --format stylish --config ../../oxlint.config.cjs src test --max-warnings 0","test":"npm run typecheck:test && vitest run","build":"tsc -b","clean":"rimraf lib tsconfig.tsbuildinfo","watch":"tsc -b -w --preserveWatchOutput","prepack":"node -e \"const m=require('./package.json'),fs=require('node:fs');const missing=[m.main,...Object.values(m.bin||{})].filter(entry=>entry&&!fs.existsSync(entry));if(missing.length){console.error('prepack '+m.name+': not built ('+missing.join(', ')+' missing). Run the build before packing: a files entry that matches nothing is skipped silently, so the tarball would ship src only.');process.exit(1);}\"","typecheck:test":"tsc --noEmit -p tsconfig.test.json"},"version":"1.0.0-next.185","_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"2fdeca71-16a8-45b4-b6d0-fd7895082c48"}},"homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","keywords":["data-server","hydranium","langium","language-server","lsp","rpc"],"//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.","//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.","repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"_npmVersion":"11.15.0","description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","directories":{},"maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"sideEffects":false,"_nodeVersion":"22.18.0","publishConfig":{"access":"public"},"_hasShrinkwrap":false,"devDependencies":{"rimraf":"^5.0.0","typescript":"^7.0.2","vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.185","@hydranium/langium":"1.0.0-next.185","@hydranium/protocol":"1.0.0-next.185","vscode-languageserver-textdocument":"^1.0.12"},"peerDependencies":{"vscode-jsonrpc":"9.0.1","@hydranium/core":"1.0.0-next.185","@hydranium/langium":"1.0.0-next.185","@hydranium/protocol":"1.0.0-next.185","vscode-languageserver-textdocument":"^1.0.12"},"//peerDependencies":"`vscode-jsonrpc` is EXACT rather than a range, because it is one link of an atomic chain with no independently movable link: `vscode-languageserver-protocol` depends on it at exactly 9.0.1, so any other value an adopter supplies is a SECOND physical copy rather than an upgrade. This wire stack breaks on copy identity rather than on structure — `ParameterStructures.auto` is a singleton compared by `===` in connection.js, so a request type built by one copy and sent over a connection owned by the other throws `Unknown parameter structure auto`. A caret or union range was rejected because npm then resolves a `vscode-jsonrpc@8.2.0` tree SILENTLY, with no diagnostic at all, and the failure surfaces only later at server init. Exact does not fail the install either — npm downgrades an unsatisfiable peer to a warning — but it is a NAMED ERESOLVE warning printing the required version beside the found one, and a hard error for anyone installing with `--strict-peer-deps`. It does NOT prevent a NESTED copy — `@eclipse-glsp/*` carries its own exact `vscode-jsonrpc@8.2.0` dependency and root `overrides` do not ship — so a consumer of the GLSP head must pin the chain in its own manifest, and docs/adopting/requirements.md carries the block to paste.","_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/data-server_1.0.0-next.185_1790957354140_0.16281076217960888"}}},"time":{"created":"2026-09-08T23:04:31.863Z","modified":"2026-10-02T16:09:14.612Z","1.0.0-next.4":"2026-09-08T23:04:32.141Z","1.0.0-next.5":"2026-09-08T23:45:44.983Z","1.0.0-next.6":"2026-09-09T09:16:39.189Z","1.0.0-next.7":"2026-09-09T11:32:01.760Z","1.0.0-next.8":"2026-09-09T11:40:12.117Z","1.0.0-next.9":"2026-09-09T12:48:12.362Z","1.0.0-next.10":"2026-09-09T14:07:07.855Z","1.0.0-next.11":"2026-09-09T14:18:15.949Z","1.0.0-next.12":"2026-09-09T15:59:27.436Z","1.0.0-next.13":"2026-09-10T08:09:48.284Z","1.0.0-next.14":"2026-09-10T09:23:13.649Z","1.0.0-next.15":"2026-09-10T09:32:17.660Z","1.0.0-next.16":"2026-09-10T09:50:28.635Z","1.0.0-next.17":"2026-09-10T10:45:56.838Z","1.0.0-next.18":"2026-09-10T11:04:21.395Z","1.0.0-next.19":"2026-09-10T13:29:38.940Z","1.0.0-next.22":"2026-09-10T20:27:06.825Z","1.0.0-next.23":"2026-09-10T20:47:19.764Z","1.0.0-next.24":"2026-09-10T21:01:37.212Z","1.0.0-next.25":"2026-09-10T21:21:17.553Z","1.0.0-next.27":"2026-09-10T21:42:44.383Z","1.0.0-next.28":"2026-09-10T21:55:46.567Z","1.0.0-next.29":"2026-09-10T22:42:44.790Z","1.0.0-next.30":"2026-09-10T22:55:52.984Z","1.0.0-next.31":"2026-09-10T23:10:28.547Z","1.0.0-next.32":"2026-09-10T23:29:45.670Z","1.0.0-next.33":"2026-09-10T23:52:37.885Z","1.0.0-next.34":"2026-09-10T23:59:46.979Z","1.0.0-next.35":"2026-09-11T07:17:24.797Z","1.0.0-next.36":"2026-09-11T07:25:49.709Z","1.0.0-next.37":"2026-09-11T07:37:22.222Z","1.0.0-next.38":"2026-09-11T07:43:45.143Z","1.0.0-next.39":"2026-09-11T08:07:55.103Z","1.0.0-next.40":"2026-09-11T08:50:52.617Z","1.0.0-next.42":"2026-09-11T10:46:35.338Z","1.0.0-next.44":"2026-09-11T12:02:57.679Z","1.0.0-next.45":"2026-09-11T12:35:37.064Z","1.0.0-next.46":"2026-09-11T13:05:13.643Z","1.0.0-next.49":"2026-09-15T11:59:48.822Z","1.0.0-next.50":"2026-09-15T12:36:34.638Z","1.0.0-next.51":"2026-09-15T12:57:06.605Z","1.0.0-next.52":"2026-09-15T14:55:55.286Z","1.0.0-next.55":"2026-09-16T12:58:56.328Z","1.0.0-next.57":"2026-09-16T15:32:40.215Z","1.0.0-next.58":"2026-09-16T15:36:28.732Z","1.0.0-next.60":"2026-09-17T08:48:50.258Z","1.0.0-next.61":"2026-09-17T11:07:45.646Z","1.0.0-next.62":"2026-09-17T13:15:47.396Z","1.0.0-next.63":"2026-09-17T13:23:22.026Z","1.0.0-next.66":"2026-09-17T21:27:23.811Z","1.0.0-next.67":"2026-09-18T07:53:21.148Z","1.0.0-next.70":"2026-09-18T11:05:43.341Z","1.0.0-next.71":"2026-09-18T11:17:17.835Z","1.0.0-next.72":"2026-09-18T12:41:53.696Z","1.0.0-next.74":"2026-09-18T14:22:38.819Z","1.0.0-next.75":"2026-09-18T15:10:01.890Z","1.0.0-next.76":"2026-09-18T20:57:38.516Z","1.0.0-next.77":"2026-09-18T21:57:20.035Z","1.0.0-next.79":"2026-09-20T15:01:43.921Z","1.0.0-next.85":"2026-09-20T21:22:44.940Z","1.0.0-next.86":"2026-09-21T07:14:55.149Z","1.0.0-next.88":"2026-09-21T08:38:12.433Z","1.0.0-next.90":"2026-09-21T10:22:04.219Z","1.0.0-next.91":"2026-09-21T10:33:11.027Z","1.0.0-next.92":"2026-09-21T12:14:53.923Z","1.0.0-next.93":"2026-09-21T13:13:59.215Z","1.0.0-next.94":"2026-09-21T13:36:14.347Z","1.0.0-next.95":"2026-09-21T14:37:15.953Z","1.0.0-next.96":"2026-09-23T17:57:25.896Z","1.0.0-next.97":"2026-09-23T18:03:19.110Z","1.0.0-next.98":"2026-09-23T18:15:16.624Z","1.0.0-next.103":"2026-09-23T18:36:12.532Z","1.0.0-next.104":"2026-09-23T18:48:07.236Z","1.0.0-next.105":"2026-09-23T18:55:22.779Z","1.0.0-next.106":"2026-09-23T19:47:08.197Z","1.0.0-next.107":"2026-09-23T20:30:14.498Z","1.0.0-next.109":"2026-09-23T23:00:17.294Z","1.0.0-next.111":"2026-09-24T13:29:50.538Z","1.0.0-next.112":"2026-09-24T14:33:11.117Z","1.0.0-next.113":"2026-09-24T15:38:25.699Z","1.0.0-next.114":"2026-09-24T16:45:15.453Z","1.0.0-next.115":"2026-09-24T21:44:39.756Z","1.0.0-next.117":"2026-09-28T21:44:16.163Z","1.0.0-next.123":"2026-09-28T22:07:24.030Z","1.0.0-next.127":"2026-09-28T22:35:21.499Z","1.0.0-next.132":"2026-09-28T22:48:09.482Z","1.0.0-next.135":"2026-09-28T22:58:35.559Z","1.0.0-next.140":"2026-09-28T23:03:34.365Z","1.0.0-next.148":"2026-09-28T23:18:06.514Z","1.0.0-next.155":"2026-09-28T23:38:03.178Z","1.0.0-next.157":"2026-09-28T23:49:11.498Z","1.0.0-next.158":"2026-09-30T08:46:33.338Z","1.0.0-next.160":"2026-09-30T10:03:05.034Z","1.0.0-next.168":"2026-09-30T14:07:06.732Z","1.0.0-next.169":"2026-09-30T15:47:12.919Z","1.0.0-next.173":"2026-10-01T13:14:14.035Z","1.0.0-next.174":"2026-10-02T07:38:36.047Z","1.0.0-next.175":"2026-10-02T07:51:20.824Z","1.0.0-next.176":"2026-10-02T10:04:00.849Z","1.0.0-next.177":"2026-10-02T11:28:40.063Z","1.0.0-next.179":"2026-10-02T12:16:53.196Z","1.0.0-next.180":"2026-10-02T12:42:11.703Z","1.0.0-next.181":"2026-10-02T12:52:38.639Z","1.0.0-next.183":"2026-10-02T13:27:54.370Z","1.0.0-next.185":"2026-10-02T16:09:14.250Z"},"bugs":{"url":"https://github.com/eclipse-emfcloud/hydranium/issues"},"author":{"name":"Hydranium Team"},"license":"MIT","homepage":"https://github.com/eclipse-emfcloud/hydranium/tree/main/packages/data-server","keywords":["data-server","hydranium","langium","language-server","lsp","rpc"],"repository":{"url":"git+https://github.com/eclipse-emfcloud/hydranium.git","type":"git","directory":"packages/data-server"},"description":"Typed-RPC protocol head for the hydranium framework. Peer of @hydranium/core/lsp and @hydranium/glsp-server; built on @hydranium/core.","maintainers":[{"name":"mfleck","email":"mfleck@eclipsesource.com"}],"readme":"# `@hydranium/data-server`\n\nThe typed JSON-RPC data head of [hydranium](../../README.md): it exposes the live\nLangium AST to non-LSP clients — form editors, tree views, code generators — as\nan adopter-defined transfer model over a `vscode-jsonrpc` `MessageConnection`.\nInstalled by the server process that already composes\n[`@hydranium/core`](../core); a client needs only\n[`@hydranium/protocol`](../protocol).\n\n## What it gives you\n\n- **One class, `DataServer`.** `new DataServer(connection, services, options)`\n  self-wires: a single `createRpcProxy` call registers the inbound\n  `DataServerProtocol` handlers and builds the outbound `DataClientProtocol`\n  proxy on the same wire. It contributes no shared-tier DI bindings — it reads\n  exclusively from `ServerSharedServices`, so there is no shared module to\n  compose.\n- **A document lifecycle over the shared workspace:** `openModelDocument`,\n  `getModelDocument`, `updateModelDocument`, `saveModelDocument`,\n  `closeModelDocument`, `watchModelDocument` / `unwatchModelDocument`, and\n  `waitForReady` for clients that must not race workspace initialisation.\n- **Client sessions per connection:** `createSession` registers a participant,\n  whose requests then write only what it has open; `createModelDocument` and\n  the all-or-none `updateModelDocuments` serve sessions only; `closeSession`, or\n  the connection closing, ends a session and closes everything it has open. See\n  [Client sessions](../../docs/concepts/client-sessions.md).\n- **Push notifications instead of polling:** `onDocumentUpdated` when a\n  subscribed document reaches the configured build phase\n  (`DataServerOptions.subscriptionPhase`, `DocumentState.Validated` by default),\n  `onDocumentSaved` on a separate channel, `onDocumentDirtyChanged` when a\n  subscribed document starts or stops differing from its file (every document\n  the head sends that it holds also carries its current `dirty`, and a\n  `textHash` of its text), `onDocumentDeleted` (a deleted document has no built\n  state to carry, and the build-phase path never runs for one),\n  `onDocumentsBuilt` once per build for the documents nobody watches — chiefly\n  those rebuilt as a cascade, which no filesystem watcher can see because their\n  own files did not change — and `onProjectsChanged` from the project registry.\n- **Projects as first-class:** `getProjects` and `getProjectForUri`, answered from\n  the framework's `ProjectManager`.\n- **An opt-in reference/naming slice** — `findReferenceCandidates`,\n  `resolveReference`, `findNextName` — implemented here but deliberately outside\n  the `DataServerProtocol` composition, so a pure data consumer does not pay for\n  it. Compose `ReferenceServerProtocol` onto the connection explicitly.\n- **A diagnostics seam,** `DataServerDiagnosticsProvider`, with the Node\n  implementation `nodeDataServerDiagnostics()` behind `./node` so the portable\n  entry keeps bundling for a browser.\n\nThe projection itself is not this package's: it delegates to `TransferEncoder`\nand `ModelService` from `@hydranium/core`, so there is no second in-memory model\nto keep in sync.\n\nFor the adopter extension path, see [Add a data-server method](../../docs/guides/data-server-method.md). It covers the typed subclass, `additionalMethods`, shared namespace, and client proxy as one wire contract.\n\n## Install\n\n```bash\nnpm install @hydranium/data-server\n```\n\nThis package bundles no runtime dependencies. Its peers must be present:\n`@hydranium/core`, `@hydranium/protocol`, `@hydranium/langium`, `vscode-jsonrpc`\nand `vscode-languageserver-textdocument`. You must already have a composed\nhydranium shared services tree and a `MessageConnection` — the socket and stdio\nlaunchers live in `@hydranium/core/node`, not here.\n\n## Exports\n\n| subpath     | holds                                                                                                          | platform                          |\n| ----------- | ---------------------------------------------------------------------------------------------------------------- | --------------------------------- |\n| `.`         | `DataServer` and its option types, plus the `DataServerDiagnosticsProvider` seam — the whole production surface. | browser-neutral                   |\n| `./node`    | `nodeDataServerDiagnostics()`, the runtime-backed half of the diagnostics seam.                                 | Node-only                         |\n| `./testing` | `makeDataServerHarness` — a real server driven in-process over a duplex connection pair.                        | Node-only (`vscode-jsonrpc/node`) |\n\n`.` is gated as browser-neutral in CI (`scripts/check-neutral-bundles.mts`). It\nstays that way through a `browser` field in `package.json` that swaps the\ndiagnostics default for a browser twin, so a bundler never follows the\n`@hydranium/core/node` import a Node host resolves — see [what \"gated neutral\" does and does not promise](../../docs/concepts/browser-hosting.md#a-note-on-what-gated-neutral-does-and-does-not-promise).\nEach subpath also has a `./lib/…` twin for consumers on\n`moduleResolution: \"Node\"`.\n\n## Getting oriented\n\nConstruct the head after the shared services tree exists and keep the returned\ninstance for `dispose`; it registers its handlers on the connection you pass and\nsubscribes to the document builder, the text-document store and the project\nmanager for its push notifications. The typed contract a client codes against —\n`DataServerProtocol`, `DataClientProtocol`, the drift-proof method-name lists and\nthe port constants — lives in `@hydranium/protocol/data`, and the generic\n`createRpcProxy` / `bindRpcMethods` machinery in `@hydranium/protocol`. The four\ndistinct meanings of \"document\" this head sits between are worth reading first:\n[`docs/concepts/document-layers.md`](../../docs/concepts/document-layers.md). See\nalso [`docs/concepts/architecture.md`](../../docs/concepts/architecture.md) and\n[`docs/concepts/head-module-maps.md`](../../docs/concepts/head-module-maps.md).\n\n## Status\n\nAlpha — pre-v0, not yet published. The API is not stable and may change without a\ndeprecation cycle. See the [repository README](../../README.md) for the current\nstatus and known limitations.\n\n## License\n\n`MIT` — see this package's [`LICENSE`](./LICENSE). Third-party notices for the\nrepository are recorded in [`NOTICE.md`](../../NOTICE.md).\n","readmeFilename":"README.md"}