LiveKit
Client SDK JS
The SDK shifted toward unifying its connection model and enabling new data capabilities. A single peer connection mode launched in v2.17.0 as the default path with fallback to the legacy dual-PC approach, addressing long-standing complexity in the RTC layer. Data tracks moved from foundational work—packet serialization and depacketizer implementations shipped across v2.17.1 and v2.17.2—to full support in v2.18.1, including configurable E2EE key sizes for the data path. Along the way, the team tightened connection state handling to prevent false mismatches during negotiation and fixed track restart cycles that triggered unwanted mute states during unmute operations.
Connection stability and logging clarity dominated March development. The SDK renamed internal log context fields from abbreviated to full names (pID to participantID) and fixed a critical issue where RTCEngine instances were being unnecessarily recreated on join, reducing overhead during connection establishment. Additional fixes addressed end-to-end encryption key index management, data stream header parsing, and track state transitions during unmute cycles.