v1.0.0-rc3

[feat] added tls.cert, tls.key, tls.ca to make it possible to specify certificate as a string on clients that would allow that (node). (#107)

v1.0.0-rc2

• [fix] downstream transports may require different default ports (wss)
• [refactor] made TransportFactory be an interface with factory, port, urlParseFn properties, enabling downstream to customize as necessary.
• [feat] added an internal option to call a function after dispatching a message to a callback/iterator to help with post message handling (ie JetStream acks).
• [feat] added the ability to store internal info on the subscription as well as defining a hook for cleanup functionality on an unsubscribe.
• [fix] linter snake_cases type issues

v1.0.0-rc1

• [fix] [nats-base-client] fixed an issue where the connection timer was created outside of any catch block, creating a possible unhandled rejection if the connection failed - #376.
• [fix] [nats-base-client] removed class field initializers as some browsers/tooling reject them - #92.
• [feat] [nats-base-client] previously a no responders error was normalized to a request error - now has its own error code - #92.
• [fix] [nats-base-client] fixed an ambiguity that triggered a re-dial loop even if waitOnFirstConnect was not specified - #96.
• [fix] [nats-base-client] fixed bug where protocol errors dispatched to a client close, this made authentication errors not fail when supposed to.
• [change] [breaking] removed headers and noResponder ConnectionOptions. The client will auto-enable them if the server provides support. This matches other clients.

v1.0.0-13

• [feat] RequestOptions have a reply field that allows a client to make a request but specify the reply subject. The reply field is only honored when noMux is specified. This allows noMux requests to operate under subscribe permissions for the client.
• [update] updated deno std@083.0
• [fix] Changed class declarations to not have field initializers in the declaration and removed static fields as downstream consumers such as browsers in nats.ws are not able to handle such constructs (safari). Deno bundler 1.4.6 emitted compatible es modules, but newer modules emit features that are not handled by Safari.
• [fix] Fixed many linter warnings

v1.0.0-12

• [fix] header that have an error in Status can now have a Description #80
• [fix] fixed publisher connection drain - client was not flushing after closing all subscriptions #82

v1.0.0-11

• [doc] added documentation on how to use authenticators
• [update] updated to deno 1.4.6 and std 0.74.0 - adopted new formatting

v1.0.0-10

v1.0.0-10

• [fix] fixed an issue with header generation that prevented JetStream from properly parsing a header #72
• [fix] fixed an issue where if a second info was sent before a connection was resolved, the client would send a second CONNECT block which the server then treated as a protocol error and followed with a disconnect. #74
• [fix] fixed an issue for Deno clients where, on reconnect gossiped servers could upgrade to TLS using IPs, which would fail the TLS upgrade due to an invalid hostname. #76

v1.0.0-9

v1.0.0-9

[security] - IMPORTANT: Previous versions of the library merged ConnectionOptions specified by the user into the Connect object sent to the server. This created the potential that unexpected properties could be leaked. This version clamps to only send options that the server requires.

[update] deno 1.4.2 and std 0.71.0

v1.0.0-8

v1.0.0-8

This release simply provides internal support to other transport implementations.

• Changed what is provided to a transport, as some transports such as websocket requires additional information in order to decide how to connect to the server
• Added the ability for a transport implementation to specify a function that pre-processes host-port/url values as defaults for ports with some protocols are protocol defined.

v1.0.0-7

v1.0.0-7

• Fixed the exporting of some internal types that became erased by the compiler downstream