[Snyk] Upgrade bottleneck from 2.17.1 to 2.19.5

[snyk-bot]

Snyk has created this PR to upgrade bottleneck from 2.17.1 to 2.19.5.

• The recommended version is 8 versions ahead of your current version.
• The recommended version was released 2 months ago, on 2019-08-03.

Release notes

• 2.19.5 - 2019-08-03
  • Fixes a minor and rare race condition in Clustering due to an inconsistent network. The only negative effects were an error message and an expired job not be retried. Thank you @gr2m for reporting this issue #132
• 2.19.4 - 2019-07-17
  • Fixes a few issues with the TypeScript type definitions.
• 2.19.3 - 2019-07-16
  • Allow directly passing the redis/ioredis module. This fixes an issue for Clustering users that bundle their app, as seen in serverless environments. Thank you @cliffkoh for the issue #130
• 2.19.2 - 2019-07-06
  • Fixed an issue when using Redis Cluster and a custom Redis client object. Thank you @marektihkan for the excellent bug report #129
  • Fixed issue with light bundle, it would broadcast a lot of annoying but harmless exceptions on the error listener. Thank you @richtera for the excellent bug report #127
  • Updated several (dev) dependencies. Bottleneck continues to have zero run time dependencies.
• 2.19.1 - 2019-06-08
  • Fixed TypeScript typings

  The "failed" event listener typings did not allow returning undefined/null or Promise<undefined>/Promise<null>.

  Thank you @dobesv for your contribution!

• 2.19.0 - 2019-06-01
  • Added the following events: received, queued, scheduled, executing and done.

  They map to Jobs Lifecycle transitions. These events are local to a limiter inside a Cluster, for performance reasons.

  Thank you @lp-wodell for the feature suggestion! #124

• 2.18.1 - 2019-05-11
  • Reduced the memory usage of queued jobs by 40%.

  This massive gain is thanks to a refactor of the engine internals. The behavior of this module should be unchanged. If Bottleneck 2.18.1 behaves differently from 2.18.0 in your application, please open an issue.

  • Expired jobs without a catch would not trigger the Node.js "Unhandled Promise Rejection" warning.

  This has been fixed and Node now correctly alerts you, as this points to a bug in your application. async/await users: wrap your jobs into a try/catch at the place where the job is await'ed. Promise users: make sure your jobs have a .catch().

• 2.18.0 - 2019-04-13

  Added Increase Intervals. Similar to the Refresh Interval, it increases a limiter's reservoir on an interval. Instead of resetting the reservoir to a specific value, it increments the reservoir by a certain value, up to an optional maximum value.

  Thanks @TheGame2500 and @tomblanchard for suggesting this feature.

• 2.17.1 - 2019-03-03

  Optimized Clustering code for use cases where short lived clients are created at a high rate.

from bottleneck GitHub Release Notes

---

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.