-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Closed
Description
Description
Been using ws
for all projects requiring WebSocket support. It is hands down the only thing worth anybody's time. Good job.
I work on a project where I am forced to use Node.js version 5.12.0 because that is the latest version still supported on Windows Vista and Windows Server 2008 R1. Because of this I am forced to use [email protected]
as version 3.0.0
drops support for my version of Node.js (the breaking changes chapter didn't mention any of this though).
Reproducible in:
version: [email protected] and forward
Node.js version(s): 5.12.0
OS version(s): All
Steps to reproduce:
Run ws
on Node.js version 5.12.0. You can download it right here https://nodejs.org/dist/v5.12.0/ .
Expected result:
I expected that it worked.
Actual result:
TypeError: Cannot read property 'connection' of undefined
at new Connection (eval at <anonymous> (D:\MDCMaxWeb\build\dev\server\main.js:251:1), <anonymous>:76:29)
at WebSocketServer.handleConnection (eval at <anonymous> (D:\MDCMaxWeb\build\dev\server\main.js:251:1), <anonymous>:609:21)
at WebSocketServer.eval (eval at <anonymous> (D:\MDCMaxWeb\build\dev\server\main.js:251:1), <anonymous>:584:18)
at emitTwo (events.js:100:13)
at WebSocketServer.emit (events.js:185:7)
at D:\MDCMaxWeb\build\dev\node_modules\ws\lib\WebSocketServer.js:88:16
at WebSocketServer.completeUpgrade (D:\MDCMaxWeb\build\dev\node_modules\ws\lib\WebSocketServer.js:270:5)
at WebSocketServer.handleUpgrade (D:\MDCMaxWeb\build\dev\node_modules\ws\lib\WebSocketServer.js:197:10)
at Server.<anonymous> (D:\MDCMaxWeb\build\dev\node_modules\ws\lib\WebSocketServer.js:87:14)
at emitThree (events.js:110:13)
Attachments:
Metadata
Metadata
Assignees
Labels
No labels