veza

What's Changed

1.2.0 (2022-01-29)

Features

• update everything in the repo (#316) (45bf8dd)

Bug Fixes

• ensure client socket is writeable before writing to it (405190b), closes #231

New Contributors

• @favna made their first contribution in https://github.com/kyranet/veza/pull/316

Full Changelog: https://github.com/kyranet/veza/compare/v1.1.0...v1.2.0

1.1.0

Added

• Exported SendOptions, BroadcastOptions, and NetworkError interfaces.

This is a final release of [email protected]. Only cleans up the dist and sets up more npm stuff for better discoverability.

Added

• Added more tests.
• Documented all the events.
• Added veza.Server and veza.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 from undefined to this.

Removed

• Removed veza.Node in favor of veza.Server and veza.Client.

Fixed

• Resolved bug from 0.6.0 where the queue was getting into data racing on extremely edge cases.

• Written more tests.
• Coverage 100%.
• Written more tests.
• And also added a shiny 100% coverage badge.

Added:

• Added handshakeTimeout option in Node.
• Added more typings.
• Added more documentation.
• Added socket.connecting, socket.connect, socket.destroy, socket.ready, socket.connect, and socket.ready.

Changed:

• Node#connectTo does not longer take an argument for the socket's name, 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 and Queue#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!

• Added Test Suite (https://github.com/kyranet/veza/issues/9).
• Disconnect previous node if there was one named the same (https://github.com/kyranet/veza/issues/12).
• Rewritten Veza to Strict TypeScript (https://github.com/kyranet/veza/issues/13).
• Nullify the socket when destroyed.
• Fixed "Cannot read property delete of undefined".