Tiago

Also I wonder if it's the heartbeat mechanism thinking that the websocket dropped. I haven't yet added a way to turn off the heartbeat mechanism completely (but I plan in...

Will be fixed in the next release (2.0.18), available shortly. Please let me know once you've had a chance to test.

Ah I see - I don't think the heartbeat mechanism will work at all in the browser, although perhaps it's also not necessary there. You can disable it as of...

This should be possible using the new client implementations in #122. The websockets API exposes a method to connect to a full websocket URL, or you could look at expanding...

Hi there - the only docs on that so far are here: https://github.com/tiagosiebler/binance#browser-usage If you include the bundled js file with a script tag on a page, you'll have a...

> Debugging this is really painstaking though as I have to replace the `silly` loglevel messages I'm interested in with console.log to get output (I haven't tried actually setting up...

> Thanks for the detailed response @tiagosiebler ! I may try to get together a PR working to resolve the issues if I have time over the next couple of...

> How to build browser binanceapi.js > > ``` > mkdir binance && cd binance > git clone https://github.com/tiagosiebler/binance.git . > npm install > npm install webpack > npm run...

You can disable the whole logging level (or customise it with your own logic) by injecting a custom logger into the websocket client: ```javascript const { WebsocketClient, DefaultLogger } =...

> just keeping track of the last websocket event received. it's not a must have for the pong events but was just curious. appreciate the response. I see, I'm open...