v1.7.1

What's Changed

• [FIX] main in package.json by @aricart in #130
• [FIX] [DOC] nats import for 1.6+ by @adhocmaster in #128

New Contributors

• @adhocmaster made their first contribution in #128

Full Changelog: v1.7.0...v1.7.1

v1.7.0

What's Changed

• [UPDATE] the nats-base-client is updated to 1.6.0. There are new features for JetStream, compatibility fixes with nats-server version 1.7.1. For more information please see https://github.com/nats-io/nats.deno/releases/tag/v1.6.0
• [FIX] hybrid bundle - this release corrects the configuration for the hybrid bundle by @aricart in #126

Full Changelog: v1.6.0...v1.7.0

v1.6.0

What's Changed

This release updates the nats-base-client (NBC) to v1.5.0

Changes to NBC library

These changes are shared by all NATS.io supported JavaScript clients.

• [FEAT] JetStream APIs for JavaScript are no longer preview. Note that Materialized views APIs are marked as beta and subject to change. by @aricart in nats-io/nats.deno#234
• [FEAT] JetStreamManager API added consumers.update(). The ConsumerUpdateConfig provides some introspection into fields that can be modified. Modifying a consumer is only supported on servers 2.6.4 or better. @aricart in nats-io/nats.deno#229
• [CHANGE] JetStreamManager API streams.update() now requires the name of the stream. The StreamUpdateConfig provides some introspection into fields that can be modified. The previous API is shimmed, however, the shim will be removed on a future release. by @aricart in nats-io/nats.deno#230 and nats-io/nats.deno#235
• [FIX] Fixed an issue where a fast path for text encoding/decoding of NATS protocol messages (non-payload) didn't handle UTF code-points (ie when using username/password that contained these characters). All encoding decoding of protocol messages now uses TextEncoder/Decoder. by @aricart in nats-io/nats.deno#238
• [CHANGE] [BREAKING] [BETA] KV keys() now returns an iterator rather than a list of keys. If using the beta API you must change your code as no shim is possible by @aricart in nats-io/nats.deno#240
• [FIX] Documentation typos. by @MrMYHuang in nats-io/nats.deno#244
• [FEAT] added support for custom reviver in JSONCodec by @tommyo in nats-io/nats.deno#242
• [FEAT] added support for KV prefix handling by @aricart in nats-io/nats.deno#239

Full Changelog: v1.5.0...v1.6.0

v1.5.0

This release updates NBC to 1.4.0, there are a couple of small fixes and enhancements. Please see https://github.com/nats-io/nats.deno/releases/tag/v1.4.0 for a complete list of changes.

What's Changed

[UPDATE] nbc to 1.4.0

Full Changelog: v1.4.1...v1.5.0

v1.4.1

What's Changed

[UPDATE] nbc to v1.3.1 the base library has a few small fixes and adds additional JetStream functionality. See https://github.com/nats-io/nats.deno/releases/tag/v1.3.0 and https://github.com/nats-io/nats.deno/releases/tag/v1.3.0 for more information
[CHORE] set node NODE_EXTRA_CA_CERTS to point to the cert to prevent rejection in #109
[FIX] changed check on peek to insure we got data before processing connect from the server #114

Full Changelog: v1.3.0...v1.4.1

v1.4.0

What's Changed

[UPDATE] nbc to v1.3.0 the base library has a few small fixes and adds additional JetStream functionality. See https://github.com/nats-io/nats.deno/releases/tag/v1.3.0 for more information

Full Changelog: v1.3.0...v1.4.0

v1.3.0

BREAKING CHANGES

This release contains a set of changes that are API-breaking for JetStream. Since the JetStream APIs on the JavaScript clients are Preview, only the minor version of the client has been bumped. Because of these changes, you should carefully read the Breaking Changes section to ensure you are not affected.

JetStream Push Consumers In Queue Groups

The Push Consumer Queue feature has changed. A new nats-server (2.4.0) is in the works that modifies how this feature works.
The new JavaScript clients have been modified to work with the new server and will fail to work with an existing server using push consumers with queue groups.

Previously it was possible to create a push consumer and properly get it working in a queue group with a regular NatsConnection#subscribe or NatsConnection#jetstream()#subscribe() if all queue subscriptions used the same queue name and no plain (non-queue) subscriptions were used.

If the mix of subscriptions and queues referenced the same consumer but provided different queue names or no queue names, the delivery of messages was incorrect and could create conditions where some messages were seen in duplicate or have unexpected side effects.

The new nats-server changes will make an old consumer configuration with a queue group a noop - the server will not send messages to the client. To enable a queue group to work on a consumer:

• The consumer configuration must specify a deliver_group matching the queue group name.
• Configurations that use the consumer with a non-matching queue group will be invalid.
• Configurations that use a queue group consumer without a queue group will be invalid.

The nats client for JavaScript on 1.2.0 and beyond, enforces the above rules, so an Error is thrown from NatsConnection#jetstream().subscribe() for configurations that try to use the queue group incorrectly.

Because an old server will not report deliver_group for the consumer, any jetstream#subscribe() that attempts to specify a queue group will fail the validation.

If you are creating nats your own nats subscription to handle the consumer, and have an old server, you may continue to do that until you upgrade the server, at which point the nets-server will stop delivering messages to your client. Please do ensure that you don't use the consumer from different queue groups in the meanwhile.

JetStreamManager#streams#getMessage(number)

This API has been removed (it was deprecated and printing console messages). To retrieve a message by its sequence,
replace with JetStreamManager#streams#getMessage({seq: number}).

JetStream SequencePair was renamed SequenceInfo

This matches changes in the server. These types are referenced from ConsumerInfo.

Other Changes

• [FEAT] Added DeliveryPolicy#LastPerSubject which allows a consumer to get the last message for each subject in a stream.

• [FEAT] PubAck now reports a domain field representing the JetStream domain if set or returning an empty string. This feature requires a newer server.

• [FIX] ConsumerConfig now have fields deliver_group, description.

v1.2.0

This release sports a number of updates enhancing the JavaScript JetStream functionality.
For a complete list of changes, see https://github.com/nats-io/nats.deno/releases/tag/v1.1.0.

v1.1.6

• [UPDATED] nbc to 1.0.8 - see https://github.com/nats-io/nats.deno/releases/tag/v1.0.8 (#435)

v1.1.4

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