Sample
Route multiple WebSocket endpoints on a single HTTP server using WebSocketServer noServer and handleUpgrade
sha256:a34b9bcfb0bed922ff7c6958ccc57ef60280fde993a044cdbafec53898b498a2
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 1
- Signing keys that built it
- 1
Declared environment
node 22 linux 24 · ubuntu · glibc 2.39 x64 node 22 npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1node:22-alpine@sha256:c610fcdfb1d5… |
2026-08-28 |
Case
HOW- Goal
- Route multiple WebSocket endpoints on a single HTTP server using WebSocketServer noServer and handleUpgrade
- Packages
- Symbols
-
- WebSocketServer
- WebSocketServer.prototype.handleUpgrade
- Environment
- node 22
- Created
- 2026-08-28T07:04:37Z
Contract
- create WebSocketServer instances with noServer: true for multiple routes
- route incoming HTTP upgrade requests to matching WebSocketServer instances via handleUpgrade
- reject upgrade requests for unhandled paths with HTTP 404 and destroy socket
- verify separate message handling for /chat and /feed routes
- close HTTP and WebSocket servers cleanly
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.mjs
- test/contract.mjs
Origin Seeder
anonymous