v0.4.7

New Features

• Updated the "engines" property of package.json to use a range (thanks @piranna).

v0.4.6

New Features

• Added target property to RTCPeerConnection events (thanks, @CharlesRA).
• Support for additional APIs in lib/browser.js (thanks, @piranna).
• Added a naïve version of getDeviceMedia that delegates to getUserMedia (thanks, @piranna).

Bug Fixes

• Although Node 14 support was confirmed in v0.4.5, it was not included in the "engines" property of package.json (thanks, @farnabaz).
• Potential fix for a crash mentioned in #637 (thanks, @thedracle).

v0.4.5

New Features

• Updated to WebRTC M81.
• Added support for Node 14.
• Added rollback support.

Bug Fixes

• RTCPeerConnection no longer raises "icegatheringstatechange" when the RTCPeerConnection is closed. Thanks, @arlolra. (#625)

Breaking Changes

• With the update from M79 to M81, the 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.

v0.4.4

New Features

• 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.

MediaStream

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

v0.4.3

New Features

• Updated to WebRTC M79.
• Added support for Node 13.
• Added support for a number of new standard APIs (see below).

RTCPeerConnection

• Added support for restartIce.
• Added support for "icecandidateerror" events.

RTCDtlsTransport

• Added support for getRemoteCertificates.

RTCRtpSender, RTCRtpReceiver & RTCRtpTransceiver

• Added support for getCapabilities to RTCRtpSender and RTCRtpReceiver.
• Added support for setParameters to RTCRtpSender.
• Added support for setStreams to RTCRtpSender (at this time, up to one MediaStream argument is supported).
• Added support for sendEncodings to RTCRtpTransceiverInit.
• Added support for setCodecPreferences to RTCRtpTransceiver.

Bug Fixes

• Fixed a bug where VideoFrame timestamps reported via RTCP were incorrect (#566). Thanks, @lonocvb.
• Fixed a bug where, in some cases, Ninja builds failed on macOS (#582). Thanks, @taylorhoward92.
• Fixed bugs related to N-API usage in recent version of Node 12 and 13.

v0.4.2

Bug Fixes

• Fix image stride issue at certain resolutions. (#536)

v0.4.1

Bug Fixes

• Fix memory leak when receiving strings over RTCDataChannel. (#528)

v0.4.0

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.

New Features

• Updated to WebRTC M74.
• Added support for Node 12.
• Added support for Electron 4 and 5.
• Added initial RTCIceTransport support (see below).
• Added initial RTCSctpTransport support (see below).
• Expanded RTCIceCandidate support (see below).

Bug Fixes

• Avoid crashing when createDataChannel fails. (#508)

Breaking Changes

• Dropped support for Node 6.
• Installing from NPM only downloads pre-built binaries. If you wish to build from source, install from the source repository. (#200)
• Unified Plan is now the default. For Plan B behavior, set the sdpSemantics RTCConfiguration property or the SDP_SEMANTICS environment variable to "plan-b".

RTCIceTransport

RTCDtlsTransport now exposes RTCIceTransport under the iceTransport property.

The following attributes are supported:

• role
• component
• state
• gatheringState

The following events are supported:

• "statechange"
• "gatheringstatechange"

RTCSctpTransport

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.

RTCIceCandidate

RTCIceCandidates now include the following attributes:

• foundation
• component
• priority
• address
• protocol
• port
• type
• tcpType
• relatedAddress
• relatedPort
• usernameFragment

v0.4.0-beta1

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.

New Features

• Updated to WebRTC M74.
• Added support for Node 12.
• Added support for Electron 5.

Bug Fixes

• Avoid crashing when createDataChannel fails. (#508)

Breaking Changes

• Dropped support for Node 6.
• Installing from NPM only downloads pre-built binaries. If you wish to build from source, install from the source repository. (#200)
• Unified Plan is now the default. For Plan B behavior, set the sdpSemantics RTCConfiguration property or the SDP_SEMANTICS environment variable to "plan-b".

v0.3.7

New Features

RTCDtlsTransport

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.

Miscellaneous

• Updated to WebRTC M73.
• Added maxPacketLifeTime getter to RTCDataChannel (#492).
• Added negotiated getter to RTCDataChannel.

Bug Fixes

• Fixed addIceCandidate queueing behavior (#498).