Doesn't work for GDAX (node) about reconnecting-websocket HOT 5 CLOSED

I have exactly the same issue with Twitch PubSub.

RWS: handleClose { shouldRetry: true }
RWS: retries count: 1
RWS: handleClose - reconnectDelay: 2125.6480950789783
RWS: connect
RWS: bypass properties
RWS: timeout

Edit: Looks like i've found the Culprit. In the connect function, a handler for 'close' is created which calls the handleClose function, which then tries to reconnect by calling connect after a delay. The issue is that the connect function has a timeout delay which does not try to reconnect upon timeout, thus it stalls. Lemme whip up a fix.

from reconnecting-websocket.

Happy to hear that!

ReconnectingWebsocket uses the standard WebSocket API

you can use .addEventListener or assign a function to onopen:
rws.onopen = () => console.log('open');

from reconnecting-websocket.

Please, don't use ws as Websocket constructor. Use the wrapper module html5-websocket as documented in the README: https://github.com/pladaria/reconnecting-websocket#using-alternative-constructor

The way ws frees resources seems to be incompatible with this library. This may change in the future, I'm planning a full rewrite.

from reconnecting-websocket.

Just wanted to note that using Html5WebSocket isn't a drop-in replacement for WebSocket. Neither .on('open'), nor .onopen works.

const ReconnectingWebSocket = require('reconnecting-websocket');
const rws = new ReconnectingWebSocket('wss://ws-feed.gdax.com', [], {
  constructor: Html5WebSocket,
  debug: true,
});

rws.onopen(() => {            // <-- TypeError: rws.onopen is not a function
  rws.send(JSON.stringify({
    type: 'subscribe',
    product_ids: ['BTC-USD'],
    channels: ['matches'],
  }));
});

I had to convert my code to use .addEventListener.

However, the connection to GDAX now does reconnect automatically, so thanks for the module! 🙌

from reconnecting-websocket.

The URL posted above appears to no longer have a section on alternate constructors: https://github.com/pladaria/reconnecting-websocket#using-alternative-constructor Can you provide guidance on the best constructor for serverside usage in node.js?

from reconnecting-websocket.