Sample
Distinguish ws package EventEmitter API and Buffer payloads from native WHATWG EventTarget WebSocket and string payloads in Node
sha256:1a1d36a350a9eb2dcd345ed3b5163cee5cc2ec75783de4b1c90f8d313b012ee7
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Distinguish ws package EventEmitter API and Buffer payloads from native WHATWG EventTarget WebSocket and string payloads in Node HOW
- Packages
- ws 8.21.3
- Environment
- node
- Created
- 2026-08-14T22:43:45Z
Contract
- assert ws inherits from EventEmitter with .on() and .ping() while native WebSocket is an EventTarget without .on() or .ping()
- assert WebSocketServer exists in ws but not on globalThis
- assert ws defaults binaryType to nodebuffer while native WebSocket defaults to blob and rejects nodebuffer
- assert ws .on('message') yields a Buffer directly (data.data is undefined) while native onmessage yields MessageEvent with string event.data
- assert ws .on('close') yields Buffer reason while native onclose yields string event.reason
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-14 · ed25519:ac1544ece1e22594