Release v2.2.0

• Supports Firebase Cloud Functions and other serverless cloud providers by inspecting req.rawBody when the body appears to already be parsed. thanks @pichsenmeister! (#90)

• Improves the example app greet-and-react. It can now persist tokens using node-localstorage, so that you don't need to install the app each time its restarted (#84). Also, a bug in the arguments for chat.postMessage() was fixed (#83). thanks @ErwinLengkeek!

Release v2.1.1

• Adds a timing safe comparison to guard from timing attacks. Thanks @episod billdybas (#77)

Release v2.1.0

• Exports a new function verifyRequestSignature({ signingSecret, requestSignature, requestTimestamp, body }). This function can be used to verify the authenticity of a request even without using the requestListener or expressMiddleware offered by this package. It's a useful utility when your application doesn't need the adapter (EventEmitter), but you don't want to reinvent the signature check. thanks @ianwsperber (#71)

v2.0.0

This releases refactors a large portion of the adapter, adds support for request signing, and fixes a lot of bugs:

• The export name is changed from createSlackEventAdapter to createEventAdapter (#37)
• Adds request signing support, discontinuing support for verification tokens. This change requires developers to now pass in a Signing Secret in to the adapter rather than a verification token. (#57)
• Decouples the adapter from express, which included adding parsing within the adapter, meaning developers no longer need to use middleware to parse the request (using something like the body-parser package)
• Documentation improvements (#41, #42, #44, #45, #46)

Release v1.0.1

This release addresses a number of bug fixes since the initial release.

• When using the waitForResponse adapter option, error events sometimes did not emit the respond() callback function (#18)
• Added a adapter.stop() method which is close the built-in HTTP server if one was started, and return a Promise which resolves after all connections have ended. (#27)
• Errors thrown inside a handler will now result in a success response to the request by default (can be overridden by using waitForResponse and passing an error to the respond() callback) (#21, #25)
• Debugging support using the DEBUG environment variable. (#19, #22)
• More tests and documentation (#23, #26)