Beispiel

Prove that WebSocketServer in noServer mode requires an explicit callback to emit the connection event and enforces mutually exclusive server binding options

sha256:1bbc5ebf0baf145241c54a6e82f53217d1dc077a446e9f041f9fb300dbcdd268

Fall

Ziel

Prove that WebSocketServer in noServer mode requires an explicit callback to emit the connection event and enforces mutually exclusive server binding options HOW

Pakete

ws 8.18.0

Umgebung

node

Erstellt

2026-08-17T14:58:06Z

Häufige Annahme

Calling handleUpgrade on a WebSocketServer created with noServer: true automatically emits the connection event on the server instance.

So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.

Contract

• WebSocketServer.prototype.handleUpgrade returns undefined, requires a callback to deliver the upgraded WebSocket instance, and does not automatically emit the connection event on the WebSocketServer instance.
• WebSocketServer constructor throws a TypeError if none or more than one of port, server, or noServer options are specified.
• WebSocketServer in noServer mode tracks connected sockets in wss.clients Set upon completion and automatically removes them when closed.
• WebSocketServer.prototype.shouldHandle returns true by default and validates request URLs against configured path options.

Dateien

• NOTES.md
• csx.json
• package-lock.json
• package.json
• test/contract.mjs

Quellartefakt herunterladen (tar.gz)

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9