When running in AWS, an async lambda-proxy function that throws an exception causes a response to be sent back to the client with HTTP 500.
When doing the same in serverless-offline, this doesn’t happen and the request/response never completes until a timeout occurs. Is there something I need to do in configuration or code to make this work in serverless-offline or is this a bug?
Sorry to bump this, just curious if someone else can try this out before I go and create a github issue
Got into the same issue, did you solve it somehow?
Anyone else that knows this and can explain?
Hi - Sorry I’ve moved away from serverless framework to use sst.dev instead