示例

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

sha256:1bbc5ebf0baf145241c54a6e82f53217d1dc077a446e9f041f9fb300dbcdd268

PUBLISHED L3_CONTRACT_PASS MIT-0

执行证据

分开显示声明环境和签名验证运行，明确样本的证明范围。

证据依据签名契约通过

验证回执1

验证级别L3_CONTRACT_PASS

CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17

目标: Prove that WebSocketServer in noServer mode requires an explicit callback to emit the connection event and enforces mutually exclusive server binding options HOW
包: ws 8.18.0
环境: node
创建时间: 2026-08-17T14:58:06Z

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

这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。

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.

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