Releases: kyranet/veza
Releases · kyranet/veza
v1.2.0
veza@1.1.0
1.1.0
Added
- Exported
SendOptions,BroadcastOptions, andNetworkErrorinterfaces.
veza@1.0.0
This is a final release of veza@0.7.0. Only cleans up the dist and sets up more npm stuff for better discoverability.
veza@0.7.0
Added
- Added more tests.
- Documented all the events.
- Added
veza.Serverandveza.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
veza@0.5.0. - Updated spec to re-include
ByteLengthinto the headers. - Document more things as private to not show in the documentation.
- Modified
Server#serve's return fromundefinedtothis.
Removed
- Removed
veza.Nodein favor ofveza.Serverandveza.Client.
Fixed
- Resolved bug from 0.6.0 where the queue was getting into data racing on extremely edge cases.
veza@0.6.0
- Written more tests.
- Coverage 100%.
- Written more tests.
- And also added a shiny 100% coverage badge.
Added:
- Added
handshakeTimeoutoption inNode. - Added more typings.
- Added more documentation.
- Added
socket.connecting,socket.connect,socket.destroy,socket.ready,socket.connect, andsocket.ready.
Changed:
Node#connectTodoes not longer take an argument for the socket'sname, also called "label". The name is now the socket's.
Removed:
Infinityis not longer an option in timeouts nor retry limits, refer to-1for the same behaviour.- Removed
Queue#nameandQueue#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!