Deepak Kumar

I have pushed v6.1.2 - this version includes both source-maps and sources. Please check if it resolves the issue.

In v7, the following changes will happen: - The minified version will not have a source map associated. - The minified version will be the default entry point.

I will add a FAQ entry for this soon. Give me few days.

I have created a branch of samples implementing this. It also implements exponential back-off, i.e., each subsequent connection attempt will after 200, 400, 800, 1600 ... ms. See the diff...

Keeping it open for a while till I create a FAQ entry.

I will suggest to use `beforeConnect`. While implementing within the library as well we should use this callback. Will you be able to do a PR, please :smile: I think...

That makes sense. It will be good to add to FAQs. I will suggest following changes: - We need not show the actual split steps - as it may vary...

I see that the underlying Websocket is not receiving the message in throttled mode. In this case, this library will not be able to solve this issue. I will suggest...

This indeed is an issue. Thanks for your detailed notes including links to appropriate documentation. I agree that it is not fixable by this library. It is understandable why browsers...

> We are facing the same problem even we set the outgoing to 0. We experiencing websocket disconnects around every minute. Do you have any workaround suggestions? Recent versions of...