0.23.0

This version marks Trystero's biggest update since initial release. The internals have been completely rewritten with minimal changes to the public API. You'll find faster, more robust peering thanks to connection sharing and offer recycling behind the scenes. The test suite has been expanded and hardened and now tests server-side use too. Trystero also has a new public face at trystero.dev.

User-facing changes

• Trystero is now split into scoped packages: @trystero-p2p/{nostr,mqtt,torrent,supabase,firebase,ipfs} plus @trystero-p2p/core. The root trystero package still defaults to Nostr.
• trystero/<strategy> imports are now deprecated compatibility entry points; migrate to @trystero-p2p/<strategy> for non-default strategies.
• joinRoom(config, roomId, onJoinError) is now joinRoom(config, roomId, callbacks). onJoinError moved to callbacks.onJoinError, and Nostr/Torrent’s old relay-reconnection flag moved into config.manualRelayReconnection.
• joinRoom() gained a new admission-handshake layer via onPeerHandshake(peerId, send, receive, isInitiator) and handshakeTimeoutMs, so apps can accept or reject peers before they become visible to getPeers(), onPeerJoin(), actions, or media callbacks. You can use this to implement your own custom identity layer with crypto keys.
• trickleIce is now a public config option and speeds up initial connections. Most strategies default to trickle ICE, while Torrent and IPFS keep it off unless explicitly enabled.
• @trystero-p2p/core now exposes createStrategy and shared types/utilities, making custom signaling strategies a supported extension point. You can use this to run a signaling relay for Trystero on any software you want. The readme shows a basic example using a simple WebSocket server.
• Media and event ergonomics improved: replaceTrack() can now send metadata, onPeerJoin() immediately replays already-active peers to late listeners, and the action name limit increased from 12 bytes to 32 bytes.
• Firebase’s getOccupants() helper was removed. This was only used by a single strategy and removing it helps keep the API surface small. You can still replicate its functionality with the Firebase API directly.
• Server-side use is now a more explicit part of the public surface: rtcPolyfill is documented/tested, and a recommended polyfill library endorsement for werift.

Performance and reliability notes

• Peer connection reuse is the biggest runtime change: when the same remote peer appears in multiple rooms, Trystero now reuses a shared underlying RTCPeerConnection instead of renegotiating per room.
  Offer pooling/reuse was overhauled, especially for tracker-style signaling, so old offers can be reclaimed and recycled instead of constantly allocating fresh peer connections.
• Large and binary sends are more resilient under backpressure, with fixes for stalled sends and related data-channel hangs.
• Relay robustness new public relay lists and better handling of repeated pings/timeouts, which should reduce churn and improve matchmaking stability.

Please share feedback, ideas, and of course, what you build with Trystero, via GitHub discussions/issues. Go forth and build a decentralized web. 🤝

0.22.0

Breaking changes

• 🪐 IPFS - removed libp2pConfig config option

Improvements

• 🐦 Nostr and 🌊 BitTorrent - new manualRelayReconnection boolean flag in config object, which will disable Trystero's automatic relay socket reconnection behavior. This is paired with two top level package exports pauseRelayReconnection() and resumeRelayReconnection(), 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

• The default bundle size is now 20% smaller, down to 8K minified 🤏
• 🐦 Nostr - updated default relays

0.21.7

• Improved reconnection rates when leaving and rejoining rooms, thanks to @jeremyckahn
• Improved type definitions

0.21.4

Improvements

• Improved WebRTC connection logic in core peer module — this should improve connection success rates
• Default bundle size (Nostr) is now 40% smaller

0.21.3

Bug fixes

• This release fixes a regression in 0.21.2 that causes connection issues in browsers

0.21.2

Improvements

• 📣 Trystero now works server-side in Node, Deno, and Bun. See this section of the readme for details. Big thanks to @vrtmrz for figuring out the final piece of the server-side puzzle!
• 🐦 Nostr - pruned dead default relays

0.21.1

Improvements

• Fix for importing Nostr strategy in Node (note: Node support is still under development)

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.