Releases: nats-io/nats.deno
Releases · nats-io/nats.deno
v1.0.1
- [fix] the reply subject was sometimes copied incorrectly when message payloads are large and not received within the same write #134
- [fix] mux subscriptions had their base inbox subject doubly initialized #135
- [feat]
DebugEvents
has been made accessible to downstream. #131 - [feat] JetStream Listers are now async iterables as well #129
v1.0.0
Changes since RC4
- [breaking] Events/DebugEvent/ErrorCode constants have been changed to follow ES5 naming conventions
- [feat] added internal functionality to support JetStream
- [feat]
MsgHdrs
always have a code - [feat] added support for JetStream (on preview). JetStream functionality is described here. Some basic examples can be found here.
- [upgrade] deno std from 0.83.0 to 0.90.0
v1.0.0-rc4
- [feat] added the
inboxPrefix
connection option to modify the names of subjects generated by createInbox() or when making requests. - [feat] the
JSONCodec
is now a generic helping the typing of the parameter or return value.
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
andnoResponder
ConnectionOptions. The client will auto-enable them if the server provides support. This matches other clients.
v1.0.0-13
- [feat]
RequestOptions
have areply
field that allows a client to make a request but specify the reply subject. Thereply
field is only honored whennoMux
is specified. This allowsnoMux
requests to operate under subscribe permissions for the client. - [update] updated deno
[email protected]
- [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
v1.0.0-11
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