Thanks @karpawich for the PR, but it's incomplete. IncomingMessage and ClientRequest don't have a body property. They are both streams, and you need to read them all to get the body of the request. Also, since Slack is using application/x-www-form-urlencoded encoded payload, you also need to parse the body once you received all the data.

It's a very good idea to add support for Node's http interface, so let me know if you want to add the handling of the request body to this PR.

I'm happy to add body parsing support!

I will make the following changes to this PR accordingly:

• add body parsing support
• create a separate test file for Express, Next.js, and http
• update the README & other documentation to reflect changes

@gverni The PR is ready for another review.

Since the validateSlackRequest function is now async, I believe that would mean a "MAJOR" version bump to 2.0.0 per Semantic Versioning because it introduces a breaking change to the API.

Let me know your thoughts. I am happy to make any final changes (including the version bump) that you request 👍

@gverni ^ bump, in case you missed my changes!

Hey @karpawich thanks for the nudge, and sorry it took me so long. I'm going to be reviewing your PR in the next couple of days! Thanks for that

Hey @karpawich thanks for the great work you did and sorry for the late feed-back. I like a lot the idea of supporting http and next.js but I'm a bit reluctant around changing it to an asynchronous module. How about adding an extra parameters for the body and have developers doing the parsing outside of this module. In that way we don't introduce any breaking change. We can use your code in getBodyFromStream() as reference in the documentation. How does that sound?

Unfortunately, I no longer have the time to make any further revisions to this PR while I focus on school.

@gverni or anyone else - if you'd like to make the final changes requested above, that'd be great! They shouldn't take too long.