Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add documentation and example of AWSLambdaReceiver
See original GitHub issueDescription
Issue #784 (PR #785) added the new AWSLambdaReceiver. This is an official, built-in receiver for AWS Lambda and should become an alternative to developer using ExpressReceiver with ServerlessExpress.
We should document this receiver by:
- Adding example code in
examples/showcasing the usage - Adding documentation for the
AWSLambdaReceiver - Updating the AWS Lambda deployment guide to reference
AWSLambdaReceiverdocumentation- We are not ready to update the guide to use the receiver (see below)
Once the AWSLambdaReceiver supports OAuth, we can also update our deployment guide to use it.
What type of issue is this? (place an x in one of the [ ])
- bug
- enhancement (feature request)
- question
- documentation related
- example code related
- testing related
- discussion
Requirements (place an x in each of the [ ])
- I’ve read and understood the Contributing guidelines and have done my best effort to follow them.
- I’ve read and agree to the Code of Conduct.
- I’ve searched for any related issues and avoided creating a duplicate issue.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Deploying to AWS Lambda - Slack | Bolt for JavaScript
1. Prepare the app for AWS Lambda. By default, our Bolt Getting Started app sample is configured to use SocketMode. Let's update the...
Read more >Document an API using the API Gateway console
To add or edit documentation for a METHOD entity, using the GET method on the root resource as an example, choose GET under...
Read more >Slack Apps with Bolt.js & Serverless - Hawkins.io
First, if you use the Lambda receiver, then you need to explicitly add installation support which uses the HTTP receiver. The docs do...
Read more >Import in node js file for aws lambda function is not working ...
But when I add an import, the whole thing, doesn't work. This works: "use strict"; const { App, AwsLambdaReceiver, WorkflowStep } = ...
Read more >Developers - Add built-in AwsLambdaReceiver - - Bountysource
Description. We have been recommending the combination of ExpressReceiver + aws-serverless-express for AWS Lambda deployments.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I tried to use the AWSLambdaReceiver as my App doesn’t need Express, but would benefit from snappier Lambda loading times. I banged my head with “TypeError: AwsLambdaReceiver is not a constructor” for some time as I was upgrading from Bolt 2.7.0 to 3.2.0 at the same time, and thought the error might be related. Finally I realized 3.2.0 doesn’t include the compiled code for AWSLambdaReceiver yet.
Would it be possible to have AWSLambdaReceiver included in the next public release even though it’s not been documented yet?
Best, Antti
Thanks to @TheManWhoStaresAtCode 's https://github.com/slackapi/bolt-js/pull/940, we can close this issue now!