The version 6.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of ws.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 6.0.0 of ws was just published.
The version 6.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of ws.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
6.0.0Breaking changes
browser (#1345).
maxPayload
option on the client. Defaults to 100 MiB (#1402).memLevel
andlevel
options. UsezlibDeflateOptions
instead. (80e2002).Commits
The new version differs by 15 commits ahead by 15, behind by 2.
1ee42fd
[dist] 6.0.0
d963003
[example] Update dependencies
38d2e8b
chore(package): update eslint-plugin-node to version 7.0.0 (#1420)
fc95793
[fix] Fix use after invalidation bug
fbd4391
[fix] Fix compatibility with Node.js 6
b354cd1
[minor] Remove no longer needed workaround for
socketPath
optionef5a8f5
[pkg] Update eslint-plugin-standard to version 3.1.0
80e2002
[major] Drop support for the
memLevel
andlevel
options92d0a2e
[major] Add
maxPayload
option for the client (#1402)9f87842
[major] Make bundlers use a browser shim that throws an error (#1345)
72bfbe8
chore(package): update bufferutil to version 4.0.0 (#1413)
5bb29ed
chore(package): update utf-8-validate to version 5.0.0 (#1415)
3bc6b96
chore(package): update eslint to version 5.0.0 (#1403)
d73885c
[major] Drop support for Node.js 4
5d90141
chore(package): update eslint-plugin-import to version 2.13.0 (#1405)
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: