v2.0.8

• [UPDATED] nbc to 1.0.8 - see https://github.com/nats-io/nats.deno/releases/tag/v1.0.8 (#435)
• [FEAT] changed consumerOpts() to take an optional ConsumerConfig enabling the ability to specify any consumer option #433

v2.0.6

[update] updated nbc to version 1.0.6, there are small number of JetStream and header issues addressed in the base library

v2.0.4

• [update] updated [email protected], for notable changes see: https://github.com/nats-io/nats.deno/releases/tag/v1.0.4

v2.0.2

• [update] nats-base-client to v1.0.2:
  • [fix] added cluster to possible properties in ServerInfo
  • [change] jetstream max_age - in StreamConfig marked as Nanos
  • [fix] omission of headers in JetStreamPublishOptions

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 [email protected]. 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