The version 2.1.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 socket.io-client.
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.
// by default, the object is recursively scanned to check whether it contains some binary data// in the following example, the check is skipped in order to improve performancesocket.binary(false).emit('plain-object', object);
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).
greenkeeper[bot]
commented
6 years ago
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 2.1.0 of socket.io-client was just published.
The version 2.1.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 socket.io-client.
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
2.1.0Matching Socket.IO 2.1.0 release notes
Features
Milestone: 2.1.0
Diff: 2.0.4...2.1.0
Commits
The new version differs by 44 commits ahead by 44, behind by 4.
3eb047f[chore] Release 2.1.0afb952d[docs] Add a note about reconnecting after a server-side disconnection74893d5[feat] Add a 'binary' flag (#1194)9701611[chore] Bump engine.io-client to version 3.2.0 (#1192)3d8f24e[test] Update travis configuratione27f38b[chore] Restore unminified distribution files (#1191)bb743c4[docs] Document connected and disconnected socket properties (#1155)f31837f[chore] Bump debug to version 3.1.0ebb0596[chore] Release 2.0.457cee21[test] Remove IE6 and IE7 tests (#1164)c58ecfc[docs] Add code examples for registered events (#1139)e9ebe36[docs] Add an example with ES6 import in the README (#1138)19f2b19[chore] Release 2.0.383fedf5[docs] Add explicit documentation for websocket transport (#1128)c0da119[docs] Update documentation (#1124)There are 44 commits in total.
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: