seratch/bolt-on-cloud-functions-for-firebase

Read this issue first - https://github.com/slackapi/bolt/issues/361

👋 I am a maintainer of all the @SlackAPI open-source projects! Also, I've been sharing small pieces of Slack app examples:

• ChatGPT Integration App
• Cloudflare AI Integration App
• Notion Integration App
• DeepL API Integration App
• New Relic Integration App

... and so on

bolt-on-cloud-functions-for-firebase's Issues

Using App export directly without ExpressReceiver

Hi,
I am wondering if you know of a way or workaround to use the default App from @slack/bolt without using the explicit ExpressReceiver as is being done in this example, and still get it to work with cloud functions. I'm asking because I want to take advantage of the built-in auth handling that you can use when just using App (https://slack.dev/bolt-js/concepts#authenticating-oauth) instead of using ExpressReceiver and re-implementing auth using the oAuth library.

Request for Guidance: Best practices for local development and production deployments

Thanks so much for putting this together! We got a bot up and running in no time using your guidelines.

One issue I am bumping into right now if trying to figure out how to do local development on a bot without interfering with a deployed production one. Do you happen to have any tips on that or best practices?

Using the processBeforeResponse flag

Hi @seratch, I am building a slack app on cloud functions (for now... cold starts are annoying...) and I think I should be using the processBeforeResponse as outlined in slackapi/bolt-js#444 but having issues figuring out how to use it. Is it as easy as just adding the option to my App constructor? Do I need to move by ack() calls to the end of my handler functions or can I keep them at the beginning?