Releases: kyranet/veza
Releases · kyranet/veza
v1.2.0
[email protected]
1.1.0
Added
- Exported
SendOptions
,BroadcastOptions
, andNetworkError
interfaces.
[email protected]
This is a final release of [email protected]
. Only cleans up the dist and sets up more npm stuff for better discoverability.
[email protected]
Added
- Added more tests.
- Documented all the events.
- Added
veza.Server
andveza.Client
. - Added CHANGELOG.md.
- Added SECURITY.md.
- Added PROTOCOL.md.
- Added documentation page, available at veza.js.org.
Changed
- Simplified event names to be more intuitive and easier to use.
- Revamped queue to use the old message split method from
[email protected]
. - Updated spec to re-include
ByteLength
into the headers. - Document more things as private to not show in the documentation.
- Modified
Server#serve
's return fromundefined
tothis
.
Removed
- Removed
veza.Node
in favor ofveza.Server
andveza.Client
.
Fixed
- Resolved bug from 0.6.0 where the queue was getting into data racing on extremely edge cases.
[email protected]
- Written more tests.
- Coverage 100%.
- Written more tests.
- And also added a shiny 100% coverage badge.
Added:
- Added
handshakeTimeout
option inNode
. - Added more typings.
- Added more documentation.
- Added
socket.connecting
,socket.connect
,socket.destroy
,socket.ready
,socket.connect
, andsocket.ready
.
Changed:
Node#connectTo
does not longer take an argument for the socket'sname
, also called "label". The name is now the socket's.
Removed:
Infinity
is not longer an option in timeouts nor retry limits, refer to-1
for the same behaviour.- Removed
Queue#name
andQueue#socket
. They're unnecessary getters.
Fixed:
- Fixed any possible outcome of an HTTP server or client being able to crash a Veza server or socket.
- Fixed reconnections not identifying correctly.
And more!