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

v1.0.0-6

v1.0.0-6

• Bumped std to 0.69.0
• Bumped CI to deno 1.4
• Fixed import/export for types to pacify deno's tsc compiler
• Fixed Msg.getPending() to provide correct count of messages still in flight.
• Bumped nkeys.js dependencies

v1.0.0-5

#v1.0.0-5

• [BREAKING] this release changes the signature of msg.respond from (payload?: Uint8Array, headers?: MsgHdrs): boolean to (payload?: Uint8Array, opts?: PublishOptions): boolean. If you are responding with only headers, you'll need to modify your code to {headers: msgHeaders}. The change is required to allow a respond specify a reply subject - APIs such as JetStream make use of this feature.

• [chore] Updated deno std to std@0.68.0

• [chore] Updated CI to use deno 1.3.3

• [chore] Replaced unused promises in tests to have a then() to pacify IDE warnings

v1.0.0-4

• [feat] subscriptions that specify a callback now throw an error if an iterator is attached to it.
• [fix] callback subscriptions, now correctly report pending and processed messages.
• [feat] connections have the property info which provides the current server info

v1.0.0-3

• updated version of nkeys.js
• added an optimization to the protocol parser that prefers uses of buffer.slices() over subarray() when running in Node. As Nodejs transposes the functionality of slice and subarray.