@slack/client v3.10.0

• RTM client can now be initialized to use rtm.connect instead of rtm.start with option useConnect: true (#344) - thanks @CharlieHess
• Adds the new Web API method: rtm.connect (#344) - thanks @CharlieHess
• Adds support for the chat.unfurl option userAuthRequired (#336) - thanks @againer
• Adds the new Web API method: im.replies (#339) - thanks @moinism
• Adds support for presence subscriptions (#350) - thanks @CharlieHess
• Improve reliability of RTM reconnects (#349) - thanks @CharlieHess
• Fixes issue with RTM reconnect not using the same options as the initial connect (#347) - thanks @CharlieHess
• Fixes out of order messages in client's request queue (#346) - thanks @chapmanc
• Fixes bug in MemoryDataStore when seaching for a user by username that does not exist in the team (#332) - thanks @frejos
• Fixes example code to work as described in the comments (#337) - thanks @lukeb-uk

@slack/client v3.9.0

Adds the new Web API method: chat.unfurl. Check out App Unfurls!

@slack/client v3.8.1

• Well, that didn't go so well, now did it? This release fixes #303

@slack/client v3.8.0

• In the past, you had to contort your callbacks to any Web API endpoint, because not all errors were propogated through the error parameter. Well, good news: We are no longer forcing you to sit uncomfortably. Server errors that result in a 200 OK + {ok: false, error:"mumble_mumble"} result are now passed through the error parameter so you can simplify your callback logic. If you want.
• Did you know that Slack will pass information on the scopes required to call a particular Web API endpoint? We do! And now you can get your hands on that very same information in your Web API callbacks too. Will help you debug and identify failed calls due to scoping issues.
• The Web API functionality has been expanded to include users.profile.[get|set]. Mind that you can only update your own profile 😉
• Did you notice that there were errors in the documentation? There were (and almost certainly still are). Several concerned readers wrote in with comments and fixes, all of which have been addressed.
• Last but not least, we have added functionality to track basic usage of this SDK. All calls to the Web API and the RTM API are made with a user agent string that identifies the version of this SDK in use, as well as system information on node version and operating system. More better, you can add to this treasure trove of analytics—we've added a function in helpers.js that you can call from your code to let us know more about your framework or bot. In the future, we will be adding this same information to a wide range of SDKs that access the Slack Platform, and releasing usage data publicly so we can all see who is winning this popularity contest.

@slack/client v3.7.0

• Don't know a user's ID? Want to find a DM with that user anyway? Now you can retrieve a DM from the memory store by username. Awesome.
• API endpoints of the form a.b.c required a bit of rather tortured code to call. We have removed the torture requirements, and you can now call them as you might expect.

@slack/client v3.6.1

• You can now use arbitrary images for your bot's avatar with incoming webhooks. Because
  your app wasn't creepy enough before.
• Previously, we had no support for HTTPS proxies. This unfortunate situation has been
  rectified, and now your bot can live behind the nastiest sorts of firewalls.

@slack/client v3.6.0

• Adds support for Incoming Webhooks
• Fixes a bug around User IDs

@slack/client v3.5.4

• Fixes a bug whereby events with fields not recognized cause a crash. Wow.
• Updated some logic around what user ids look like.

@slack/client v3.5.3

• Fixes a bug in the package.json published by 3.5.2.

@slack/client v3.5.2

• Updating the links in package.json so that you don't need SSL credentials to pull down the github repo.