build(deps): bump node-nats-streaming from 0.0.51 to 0.3.2

[dependabot-preview]

Bumps node-nats-streaming from 0.0.51 to 0.3.2.

Release notes

Sourced from node-nats-streaming's releases.

v0.3.2

• This release specifies the latest version of the peer nats library, correcting one serious issue for users of TLS connections and timeouts on v0.3.0. For more information see https://github.com/nats-io/nats.js/releases/tag/v1.4.9.

v0.3.0

• Implemented getRedeliveryCount() on a message which returns the number of times the message has been redelivered. This requires nats-streaming-server v0.17.0 - See #155
• Fixed an issue related to the client lifecycle when the client is created with an existing nats connection, the connect handler was not triggered, thus the client would appear to hang.
• Exposed recent connection properties in the typescript bindings. See #145.
• Adopted standardjs for project formatting
• Updated dependencies

v0.2.6

[FIX] Changed protobuf generation to commonjs_strict removing the global variable global conflict for applications that use other protobuf-based libraries.

v0.2.4

[NEW] subscriptions now emit errors/timeout event notifications [NEW] tokenhandler options are now forwarded to the underlying nats connection options.

v0.2.2

connectTimeout changes

• internal request/reply timeouts of the stan protocol now have their timeouts specified by the connectTimeout property as done in the go-nats-streaming client.

ES6 Changes

• changed var to const/let. Use of arrow functions everywhere it could simplify code.

Tests

• move to nyc from istanbul exposed a number of tests hanging because timers were not properly closed under some conditions (this required changes in node-nats), as well as insuring that all tests call close() on the connection.

Updated Samples/Bench tools

• the samples and tools hadn't been updated or reviewed since initially written. They received some love.

Dependency updates

• updated all dev depedencies
• replaced istanbul with nyc

v0.2.0

• [CHANGE] The properties maxPingOut and pingInterval were renamed to stanMaxPingOut and stanPingInterval to prevent nats property shadowing. Any client that used these properties will have to be updated to use the new ones.

• The index.d.ts was updated: the StanOptions now extend most ClientOpts from node-nats. AckHandlerCallback now properly declares the error argument as possibly undefined.

v0.1.0

This release introduces client-side pings to help keep track of streaming server connections. The feature introduces 2 new connection options:

• pingInterval which controls the number of milliseconds between client pings to the server (default is 5000 milliseconds)
• maxPingOut the number of unanswered ping requests before the connection_lost event is emitted on the client notifying that the connection from the server was lost.

You can read more about it here: https://github.com/nats-io/node-nats-streaming#connection-status.

Note that this release makes one change to client connection options. By default, NATS connections that are created by the library will set maxReconnectAttempts to infinite.

Commits

• 82295b0 0.3.2
• e1fc643 updated to nats.js 1.4.9 (#162)
• c68e133 updated nats.js and dev dependencies (#159)
• da4b271 dependency updates (#156)
• 9541d18 Bump minimist from 1.2.0 to 1.2.2 (#158)
• 8a4cb86 Bump acorn from 7.1.0 to 7.1.1 (#157)
• 86ab23a redelivery count (#155)
• c7a288c Fix #153 - handle nats connections that are already connected (#154)
• fec6cbe FIX #146 - for some reason when running on docker, require('../package) fai...
• bfa731b forwarding of newer nats connection properties (#145)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)