All notable changes will be documented in this file.
-
added: ability to change json stringify / json parse methods for DataConnection #592
-
removed:
peerBrowserfield fromdataConnectionbecause unused -
fixed: lastServerId and reconnect #580 #534 #265
-
removed: deprecated
RtpDataChannelsandDtlsSrtpKeyAgreementoptions -
removed: grunt from deps, upgrade deps versions
-
removed: Reliable dep because modern browsers supports
RTCDataChannel.orderedproperty -
added: TURN server to default config
-
fixed: emit error message, then destory/disconnect when error occured
-
fixed: use
peerjs-js-binarypackinstead ofjs-binarypack -
fixed: sending large files via DataConnection #121
- fixed: 'close' event for DataConnection #568
- add pingInterval option
- fixed: memory leak in DataConnection #556
- fixed: missing sdpMid in IceServer #550
- updated: old @types/webrtc dependency #549
- fixed: readyState of undefined #520
- fixed: call sdpTransform in Answer #524
- fixed: sdpTransform does not apply to makeAnswer SDP #523
Almost all project was refactored!!!
- removed: xhr long-pooling #506
- changed: fetch api instead of xhr
- added: heartbeat #502
- fixed: destroy RTCPeerConnection #513
- fixed: MediaStream memory leak #514
- typescript: First commit (0c77a5b)
- fixed typo in README (f1bd47e)
- Patch for #246, which started as of Chrome 38.
- Browserify build system
- Fixed a bug where
disconnectedwould be emitted for XHR requests that were aborted on purpose.
- Allow an external adapter to be used (for
RTCPeerConnectionand such). (Thanks, @khankuan!) - Fixed a bug where
_chunkedDatawas not being cleared recursively, causing memory to be eaten up unnecessarily. (Thanks, @UnsungHero97!) - Added
peer.reconnect(), which allows a peer to reconnect to the signalling server with the same ID it had before after it has been disconnected. (Thanks, @jure, for the amazing input :)!) - Added previously-missing error types, such as
webrtc,network, andpeer-unavailableerror types. (Thanks, @mmis1000 for reporting!) - Fixed a bug where the peer would infinitely attempt to start XHR streaming when there is no network connection available. Now, the peer will simply emit a
networkerror and disconnect. (Thanks, @UnsungHero97 for reporting!)
- The following changes are only compatible with PeerServer 0.2.4.
- Added the ability to specify a custom path when connecting to a self-hosted PeerServer.
- Added the ability to retrieve a list of all peers connected to the server.
- Chrome 31+/Firefox 27+ DataConnection interop for files.
- Deprecate
binary-utf8in favor of faster support for UTF8 in the regularbinaryserialization. - Fix
invalid-keyerror message.
- Workaround for hitting Chrome 31+ buffer limit.
- Add
.bufferSizeto DataConnection to indicate the size of the buffer queue. - Add
.dataChannelto DataConnection as an alias for._dc, which contains the RTCDataChannel object associated with the DataConnection. - Update BinaryPack dependency.
- Fix bug where chunks were being emitted.
- Fix file transfer issue in Chrome by chunking for data over 120KB.
- Use binary data when possible.
- Update BinaryPack dependency to fix inefficiencies.
- Fix exceptions when peer emits errors upon creation
- Remove extra commas
- Use SCTP in Chrome 31+.
- Work around Chrome 31+ tab crash. The crashes were due to Chrome's lack of support for the
maxRetransmitsparameter for modifying SDP. - Fix exceptions in Chrome 29 and below.
- DataChannels are unreliable by default in Chrome 30 and below. In setting
reliable to
true, the reliable shim is used only in Chrome 30 and below.
- Updated docs and examples for TURN server usage
- Fixed global variable leak
- DataConnections now have reliable: false by default. This will switch to on when reliable: true works in more browsers
- Support for WebRTC video and audio streams in both Firefox and Chrome.
- Add
util.supports.[FEATURE]flags, which represent the WebRTC features supported by your browser. - Breaking: Deprecate current
Peer#connectionsformat. Connections will no longer be keyed by label and will instead be in a list.
- Breaking: Deprecate
Peer.browserin favor ofutil.browser. - Additional logging levels (warnings, errors, all).
- Additional logging functionality (
logFunction). - SSL option now in config rather than automatic.
- Fix bug, no error on Firefox 24 due to missing error callback.
- TLS secure PeerServers now supported.
- Updated version of Reliable shim.
- Fix bug, no error when .disconnect called in before socket connection established.
- Fix bug, failure to enter debug mode when aborting because browser not supported.
- Peer.browser to check browser type.
- Update Reliable library and fix Reliable functionality in Chrome.
- Firefox compatibility for Firefox Nightly.
- Misc bug fixes.
- Warning: this build changes the error of type
peer-destroyedtoserver-disconnected. Firefox compatibility.- Pushed back due to volatility of Firefox Nightly DataChannel APIs.- Browser detection added. If an incompatible browser is detected, the
browser-incompatibleerror is emitted from thePeer. - Added a
.disconnect()method toPeer, which can be called to close connections to the PeerServer (but not any active DataConnections).
- Warning: this build introduces the following API changes that may break existing code.
peer.connectionsis no longer a hash mapping peer IDs to connections.- Connections no longer emit errors from
PeerConnection;PeerConnectionerrors are now forwarded to thePeerobject.
- Add support for multiple DataConnections with different labels.
- Update Reliable version to support faster file transfer.
- Fix bug where using XHR streaming to broker a connection occasionally fails.
- Add experimental
reliablemessaging option. See documentation. - Fix bug where the ID /GET request was cached and so two Peers created simultaneously would get the same ID: See issue.
- Add support for relative hostname. See documentation.