/**
 * Early receiver-transform installation.
 *
 * Since Chrome ~141, assigning `RTCRtpReceiver.transform` only takes effect
 * when the assignment happens before the receiver's VideoReceiveStream has
 * settled and frames started flowing. In practice that means the transform
 * must be installed synchronously right after `setRemoteDescription` resolves,
 * before the local answer is created. Neither LiveKit's `TrackSubscribed`
 * event nor the peer connection `track` event fires early enough anymore —
 * frames then keep flowing to the decoder and are silently dropped there.
 *
 * To hit that window we wrap `RTCPeerConnection.prototype.setRemoteDescription`
 * (the only JS-observable point that is early enough) and notify registered
 * handlers synchronously when an SRD resolves. The wrapper is installed lazily
 * on first registration and handlers are scoped to LiveKit-track m-lines, so
 * peer connections unrelated to a LiveKit room are not affected.
 *
 * @internal
 * @packageDocumentation
 */
export {};
//# sourceMappingURL=early-transform.d.ts.map