v0.3.2

• This release specifies the latest version of the peer nats library, correcting one serious issue for users of TLS connections and timeouts on v0.3.0. For more information see https://github.com/nats-io/nats.js/releases/tag/v1.4.9.

v0.3.0

• Implemented getRedeliveryCount() on a message which returns the number of times the message has been redelivered. This requires nats-streaming-server v0.17.0 - See #155
• Fixed an issue related to the client lifecycle when the client is created with an existing nats connection, the connect handler was not triggered, thus the client would appear to hang.
• Exposed recent connection properties in the typescript bindings. See #145.
• Adopted standardjs for project formatting
• Updated dependencies

v0.2.6

[FIX] Changed protobuf generation to commonjs_strict removing the global variable global conflict for applications that use other protobuf-based libraries.

v0.2.4

[NEW] subscriptions now emit errors/timeout event notifications
[NEW] tokenhandler options are now forwarded to the underlying nats connection options.

v0.2.2

connectTimeout changes

• internal request/reply timeouts of the stan protocol now have their timeouts specified by the connectTimeout property as done in the go-nats-streaming client.

ES6 Changes

• changed var to const/let. Use of arrow functions everywhere it could simplify code.

Tests

• move to nyc from istanbul exposed a number of tests hanging because timers were not properly closed under some conditions (this required changes in node-nats), as well as insuring that all tests call close() on the connection.

Updated Samples/Bench tools

• the samples and tools hadn't been updated or reviewed since initially written. They received some love.

Dependency updates

• updated all dev depedencies
• replaced istanbul with nyc

v0.2.0

• [CHANGE] The properties maxPingOut and pingInterval were renamed to stanMaxPingOut and stanPingInterval to prevent nats property shadowing. Any client that used these properties will have to be updated to use the new ones.

• The index.d.ts was updated: the StanOptions now extend most ClientOpts from node-nats. AckHandlerCallback now properly declares the error argument as possibly undefined.

v0.1.0

This release introduces client-side pings to help keep track of streaming server connections. The feature introduces 2 new connection options:

• pingInterval which controls the number of milliseconds between client pings to the server (default is 5000 milliseconds)
• maxPingOut the number of unanswered ping requests before the connection_lost event is emitted on the client notifying that the connection from the server was lost.

You can read more about it here: https://github.com/nats-io/node-nats-streaming#connection-status.

Note that this release makes one change to client connection options. By default, NATS connections that are created by the library will set maxReconnectAttempts to infinite.

v0.0.52

• FIX nats-io/nats.node#244 - (port connection property not being honored)
• Updated dependencies

minor fixes

• Added queue group to typescript subscribe definitions #79
• Fixed ack subject format #82

v.0.0.50

[FIX] #71 Event for disconnect was not mapped
[FIX] #75 Fixes:

• package.json constraints allow for nodejs 10 and better
• small fixes to client close() some cases where events were emitted, didn't return, running into NPEs.