onConnect is called when the WebSocket error event has fired

[jackkleeman]

client.js is meant to call onConnect on line 31 if the WebSocket open event fires. The WebSocket error event is listened to by source.js which on line 41 calls the onConnect callback with this event. This means that functions waiting for connection establishment proceed despite the websocket being in an errored state.

[jackkleeman]

Actually I suspect this is expected behaviour, looks like js-libp2p (a downstream library I work with) wasn't checking for errors when onConnect is called.