v2.0.1

[update] updated to nats-base-client v1.0.1, this release contains an important fix regarding the munging of reply subjects on messages that were received during different socket reads. This would cause clients to timeout when expecting a response.

v2.0.0

NATS 2.0.0 Release

• [feat] The 2.0 release has many changes and it is not API compatible with nats@1.x.x. For more information, please see the migration document.
• [feat] The 2.0 release adds support for JetStream (on preview). JetStream functionality is described here. Some basic examples can be found here.
• [breaking] If you were using release candidates, the Events/DebugEvent/ErrorCode constants have been changed to follow ES5 naming conventions.

v1.4.12

[FIX #367] tls.connect callback performed a flushPending which didn't strip subs. (#368)

v1.4.9

Release Notes

• FIX #340 - If tls was used and the connect timeout option was used, a leaked timer closed the connection.
• FIX #347 - Fixed an issue where host:port specified in servers were not expanded to NATS urls, failing the dial.
• FIX #349 - Bumped control line to match default for the server (4K)

v1.4.8

• Fixed an issue where the inbound buffer was nullified whenever there was a disconnect or some sort of library initiated socket close. If the client code had a timer or interval that executed before the client started its reconnection sequence, the client code could get a null pointer exception. - See #336

v1.4.6

• Updated NUID dependency
• Added a check on the inbound buffer to test if the buffer was null, in some cases this could evaluate and NPE. See #330
• Updated dev dependencies

v1.4.2

• New option #309 added the timeout connection option, which allows the client to specify how long to wait from the initial TCP dial to the first PONG from the server. If the first PONG is not received within the specified time, the connection fails.
• FIX #319 and #318 - Reworked reconnectTimeWait and maxReconnects to match other clients. maxReconnect is now per server, and reconnectTimeWait is based on server last connection.
• FIX #321 on reconnect any unsubscribe requests are resent to the server.
• FIX #323 - cleaned up pending buffer on disconnect. If the client disconnects from a connected session, pending messages are discarded as the buffer could contain partials. Also any pending flush callbacks will be called with a DISCONNECT error. After resetting the pending buffer, the client can subscribe and queue new messages, which will be delivered on the next reconnect. Intermediate failed dials do not reset the pending buffer or fail flush callbacks.
• FIX #326 fixed subscription ids to start at 1
• Fixed an issue where if the client emitted an errror (when it failed to connect to a server), the TCP stream would be closed, but the client was not closed preventing the application from terminating.
• updated dependencies

v1.4.0

• Added handling for TLS preflight OpenSSL checks, which are thrown instead of exposed as events. See #310. Thanks @labsvisual.

• Fixed an issue where inbound message processing was aborted when a permissions error was encountered, but connection remained open. See #291.

• Normalized official connection properties in tests and Readme.md. Added documentation on connection properties, and emitted events.

• Fixed an issue affecting clients using JSON where if the payload was a number, the number would incorrectly be interpreted as a timeout parameter on request operations (#292)

• Exposed missing connection options in typescript interface (#302)

• Adopted standard-js for all nats-io javascript projects

• Fixed samples to have copyright after the shebang

• Added samples as commands, enabling use of via npx node-[pub|sub|req|rep]

v1.3.0

• Adds support for draining connections and subscriptions

v1.2.10

FIX #263 Typescript definitions missing return type for requestOne