Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / appuri/robust-websocket issues and pull requests

#26 - Enforcing the usage of new

Issue - State: open - Opened by AlexisTM about 6 years ago

#25 - Point to new repo location

Pull Request - State: closed - Opened by keithamus about 6 years ago - 3 comments

#24 - fix: be defensive around use of window.WebSocket

Pull Request - State: closed - Opened by keithamus about 6 years ago - 1 comment

#23 - fix: only call `send` when it is available

Pull Request - State: closed - Opened by keithamus about 6 years ago - 2 comments

#22 - Release 0.3.0

Pull Request - State: closed - Opened by keithamus almost 7 years ago - 2 comments

#21 - Allow attaching to connenctivity events to be disabled.

Pull Request - State: closed - Opened by alexjeffburke about 7 years ago - 4 comments

#20 - allow shouldReconnect to opt into handling 1000 events

Pull Request - State: closed - Opened by felipeochoa over 7 years ago - 1 comment

#19 - Added constants to fully comply to standard websocket

Pull Request - State: open - Opened by hktonylee over 7 years ago - 4 comments

#18 - Missing support for Node.js

Issue - State: open - Opened by bennycode over 7 years ago - 6 comments

#17 - Coalesce falsey protocols to undefined. Fixes #12

Pull Request - State: closed - Opened by nathanboktae over 7 years ago

#16 - Reconnect function doesn't work when connect fails with error code 500/503

Issue - State: closed - Opened by hyee over 7 years ago - 1 comment

#15 - Fix clearing of pending reconnects

Pull Request - State: closed - Opened by kiejo over 7 years ago

#14 - Reconnect on 1000

Issue - State: closed - Opened by felipeochoa over 7 years ago - 8 comments

#13 - Possible bug

Issue - State: closed - Opened by felipeochoa over 7 years ago - 1 comment

#12 - Sent non-empty 'Sec-WebSocket-Protocol'

Issue - State: closed - Opened by Falseclock over 7 years ago - 8 comments

#11 - Confusing readme

Issue - State: open - Opened by Falseclock over 7 years ago

#10 - Event.currentTarget is readOnly

Issue - State: closed - Opened by catamphetamine almost 8 years ago - 1 comment

#9 - ReferenceError: navigator is not defined

Issue - State: closed - Opened by catamphetamine almost 8 years ago - 4 comments

#8 - Clarify docs on reconnecting

Issue - State: closed - Opened by catamphetamine almost 8 years ago - 9 comments

#7 - added missing semicolon

Pull Request - State: closed - Opened by john-doherty almost 8 years ago - 3 comments

#6 - Documentation needed

Issue - State: closed - Opened by john-doherty almost 8 years ago - 5 comments

#5 - don't rely on `this` being the global object

Pull Request - State: closed - Opened by jgillich almost 8 years ago - 1 comment

#4 - Chrome v42

Issue - State: closed - Opened by swilsonnc almost 8 years ago - 6 comments

#3 - 0.2.0 no longer works for me

Issue - State: closed - Opened by dubiousdavid almost 8 years ago - 5 comments

#2 - Publish latest to npm

Issue - State: closed - Opened by dubiousdavid about 8 years ago - 4 comments

#1 - Looks interesting but seems to depend on the browser environment

Issue - State: closed - Opened by mschipperheyn about 8 years ago - 7 comments