Jonas Gloning

I published a new beta release that should respect the ordering (except for `File/Blob`s) Please test it! You can get it on npm via ```bash npm i peerjs@rc ```

Please don’t feel obligated to try, but maybe you could call `file.arrayBuffer()` before passing it to PeerJS. Then there’s no `async` operation left in the `send` operation, and the order...

Hi @brianismeta, WebRTC’s data channels use _SCTP_, not UDP or TCP. If you want to keep the order of messages, you’ll have to set `{reliable: true}` in the `Peer.connect` call....

Starting from `v1.5` (just published) you can use `conn.close({flush: true})` to drain all data before closing the connection.

Fixed in `v1.5`.

Clients with different IP versions can’t connect to each other on layer 3; how could we expect them to form a p2p WebRTC connection? If you want to bridge different...

Thank you for your detailed report, @StoneCypher. Parcel@1 had some long-standing bugs that weren’t fixed because the engineering capacity was bound for version 2. It was the same for PeerJS:...

Can someone provide me with some code to reproduce this issue? It's not happening on my machine with Firefox on macOS. Maybe it is something OS-specific, and only happens on...

@vsypko You are not using PeerJS, right? I can’t see how this is relevant. But your config is [missing a TURN server](https://github.com/vsypko/hockeyteam-client/blob/3fef1cd2c27fdf6ecd54f6a487b4eef993a1e035/src/components/services/audioChatService.js#L9). Just add one to the config array and...

I guess this was just a temporary problem with the TURN server at the time. I’m closing this. If someone sees this error again, even though they are using an...