Releases: dmotz/trystero
0.22.0
Breaking changes
- πͺ IPFS - removed
libp2pConfigconfig option
Improvements
- π¦ Nostr and π BitTorrent - new
manualRelayReconnectionboolean flag in config object, which will disable Trystero's automatic relay socket reconnection behavior. This is paired with two top level package exportspauseRelayReconnection()andresumeRelayReconnection(), which allows you to control when Trystero auto-reconnects sockets. Additionally, Trystero will no longer attempt to reconnect sockets when the browser appears to be offline. Thanks to @vrtmrz for implementing. - πͺ IPFS - updated strategy, now reliably working and passing test suite
0.21.8
0.21.7
- Improved reconnection rates when leaving and rejoining rooms, thanks to @jeremyckahn
- Improved type definitions
0.21.4
0.21.3
0.21.2
0.21.1
0.21.0
Improvements
- New, modernized RTCPeerConnection abstraction
- Significantly smaller build sizes
- New
joinRoom()config object options:rtcPolyfill- Use this to pass a custom RTCPeerConnection-compatible constructor. This is useful for running outside of a browser, such as in Node (still experimental, not working yet).turnConfig- Specifies a custom list of TURN servers to use (see Connection issues section). Each item in the list should correspond to an ICE server config object. When passing a TURN config like this, Trystero's default STUN servers will also be used. To override this and use both custom STUN and TURN servers, instead pass the config via the above rtcConfig.iceServers option as a list of both STUN/TURN servers β this won't inherit Trystero's defaults.
0.21.0-beta.1
This beta release introduces a new, homegrown way of handling RTCPeerConnection instances behind the scenes. Trystero previously used simple-peer which is mostly unmaintained and showing its age. The new peer management code uses modern techniques, makes the build significantly lighter, and allows more flexibility for the project, like getting Trystero working in Node (see the new rtcPolyfill option for details).
If you use Trystero in your projects, please test this new beta version and report any issues you find. If you encounter a problem, be sure to confirm the issue does not occur on the latest stable version (0.20.1) under the same network conditions (e.g. peer A on network 1 <-> peer B on network 2).
Try this release via npm i trystero@beta.