v0.8.0

This release updates the default request-reply strategy to use a single global subscription per client. Instead of creating a subscription per request() or requestOne(), a single inbox with a wildcard subscription is multiplexed for all request-reply operations.

The options of the request() method now support a timeout property. When specified, the timeout defines the number of milliseconds to wait for the specified number of messages (via the max property) or an error is dispatched. If max is not specified the client code is responsible to call unsubscribe() to cancel the internal timeout. As previously if max number of messages or timeout is triggered, the handler for responses is auto-removed.

The client option useOldRequestStyle when set to true, will use the legacy request-reply mechanism of creating a new inbox subscription and publishing a request message per call.

v0.7.29

Reverted changes from typescript where TlsOptions converted to TlsServerOptions and back to TlsOptions.
Fixed an issue where an outstanding client heartbeat timer prevented node from exiting on nats.close()

v.07.25

This release may affect typescript users that are not on the latest version.
NodeJS types changed TlsOptions to TlsServerOptions
See DefinitelyTyped/DefinitelyTyped@e00c711

v0.7.24

tscript exports (#167)

v0.7.20

Merge pull request #147 from nats-io/tls-reconnect-leaks

- [FIX] #145 - when using TLS reconnects would fail because of listener leaks (events firing on leaked streams)

- [FIX] node client fired error on any protocol error. Some protocol errors such as 'stale connection' should have initiated a reconnect.

- [FIX] if a client attempted to publish/subscribe to a subject for which it had no permission, an error was generated. New event ('permission_error') will now be sent to the client.

v0.7.2

Merge pull request #111 from nats-io/versionbump

Version bump for support 'preserveBuffers' option.

v0.6.8

Release v.0.6.8