node-webrtc is a Node.js Native Addon that provides bindings to WebRTC M87
target
property to RTCPeerConnection events (thanks, @CharlesRA).lib/browser.js
(thanks, @piranna).getDeviceMedia
that delegates to getUserMedia
(thanks, @piranna).dtx
, ptime
, and codecPayloadType
parameters to RTCRtpEncodingParameters no longer take affect. They've also been removed from the WebRTC 1.0 specification (see here). Although this is technically a SemVer-breaking change, few users of this library are depending on the removed functionality, and I prefer not to increment the version number at this time.addTrack
now supports multiple MediaStream arguments (#548). Additionally, MediaStreams can now be constructed with arbitrary IDs. For more information, see below. Thanks, @csheely and @sgodin.setStreams
now supports multiple MediaStream arguments.MediaStreams in node-webrtc can be constructed with arbitrary IDs. For example, the following MediaStream, stream
, has its ID set to "foo".
const stream = new MediaStream({ id: 'foo' });
stream.id === 'foo'; // true
restartIce
.getRemoteCertificates
.getCapabilities
to RTCRtpSender and RTCRtpReceiver.setParameters
to RTCRtpSender.setStreams
to RTCRtpSender (at this time, up to one MediaStream argument is supported).sendEncodings
to RTCRtpTransceiverInit.setCodecPreferences
to RTCRtpTransceiver.node-webrtc is now implemented using N-API, which is ABI stable across Node releases. This means we can now ship fewer binaries while supporting a potentially greater number of Node releases. As of 0.4.0, node webrtc targets N-API version 3.
createDataChannel
fails. (#508)sdpSemantics
RTCConfiguration property or the SDP_SEMANTICS
environment variable to "plan-b".RTCDtlsTransport now exposes RTCIceTransport under the iceTransport
property.
The following attributes are supported:
role
component
state
gatheringState
The following events are supported:
RTCPeerConnection now exposes RTCSctpTransport under the sctp
property.
The following attributes are supported:
transport
state
The following attributes are partially supported:
maxMessageSize
(always null
)maxChannels
(always null
)The "statechange" event is also supported.
RTCIceCandidates now include the following attributes:
foundation
component
priority
address
protocol
port
type
tcpType
relatedAddress
relatedPort
usernameFragment
node-webrtc is now implemented using N-API, which is ABI stable across Node releases. This means we can now ship fewer binaries while supporting a potentially greater number of Node releases. As of 0.4.0, node-webrtc targets N-API version 3.
createDataChannel
fails. (#508)sdpSemantics
RTCConfiguration property or the SDP_SEMANTICS
environment variable to "plan-b".RTCRtpSender and RTCRtpReceiver now provide access to RTCDtlsTransport via the transport
property (initially null
). Currently, RTCDtlsTransport only supports the state
property, the "statechange" event, and the "error" event.
maxPacketLifeTime
getter to RTCDataChannel (#492).negotiated
getter to RTCDataChannel.addIceCandidate
queueing behavior (#498).