LoginSign Up
← Back to all sparks
P

PeerJS

MEETINGS
Velocity0.0

Simple peer to peer data video and audio calls in the browser

peerjs.com ↗

PeerJS keeps publishing release candidates that restate the same two fixes.

webrtcpeer-to-peerjavascriptrelease-candidatesdormant
◆Current state
Every entry in PeerJS's feed is a release candidate, and each one repeats the bug list of the one before it — the unreliable close event and the data channel ordering fix appear in all four, spanning fourteen months. The genuinely new content per release is thin: a CSP fix removing the need for unsafe-eval, Blob support inside nested objects, and dependency updates. The most recent publication is from April 2024.
◆Where it's heading
The changelog reads as a project maintained rather than developed, and one that never quite finishes a release cycle — candidates accumulate, notes carry forward, and stable releases do not appear in this feed. For a WebRTC wrapper this is a specific kind of risk: the browser layer underneath moves regardless, and the fixes that do land here are reactions to it, such as dropping unsafe-eval so the library survives strict Content Security Policies.
◆Prediction
There is no signal in these entries about what comes next, and no publication in roughly two years; the honest read is that the release cadence has stopped rather than that a particular change is pending.

◆Recent moves

  1. 2y ago

    v1.5.3-rc.1 drops the unsafe-eval requirement

    The newest content here is the removal of the unsafe-eval requirement and two navigator-is-not-defined fixes, which together let the library run under strict Content Security Policies and in non-browser contexts. The rest of the note restates fixes carried forward from earlier candidates.

    View source ↗
  2. 2y ago

    v1.5.2-rc.1 supports Blobs nested in objects

    Adds support for Blobs nested inside objects, closing a serialization gap that silently broke structured payloads. The other two entries in the note are repeats from the previous candidate.

    View source ↗
  3. 2y ago

    v1.5.0-rc.1 fires close on the remote peer for MediaConnection

    The close event now fires on the remote peer for MediaConnection, completing a long-open issue, alongside webrtc-adapter and binarypack updates. Data channel ordering appears again here having already been listed in the previous candidate.

    View source ↗
  4. 3y ago

    v1.4.8-rc.1: dependency updates and audit fixes

    The first candidate in this window, and the origin of the two fixes every later note repeats: unreliable close events and out-of-order data channel sends. Its own distinct content is dependency updates and an npm audit pass.

    View source ↗