serverless-express icon indicating copy to clipboard operation
serverless-express copied to clipboard

Run Express and other Node.js frameworks on AWS Serverless technologies such as Lambda, API Gateway, Lambda@Edge, and more.

Results 102 serverless-express issues
Sort by recently updated
recently updated
newest added

Dear Reader, I have gotten the following error when trying to configure a function to run async, running it sync does work. Any ideas why this is happening? ``` {...

When programmatically invoking graphql handler in apollo-server-lambda v3, I receive the following error message: "POST body missing, invalid Content-Type, or JSON object has no keys.". After reviewing the issue, I...

For some reason, the API Gateway V1 response does not include the `headers` field. It converts the input headers to `multiValueHeaders`. This is a breaking change from `aws-serverless-express` and something...

I have a pretty standard implementation using the following: ```typescript import serverlessExpress from '@vendia/serverless-express'; import { app } from '../app/app'; export const handler = serverlessExpress({ app }); ``` and an...

Hello, and first of all thanks for the very nice library :). I have a simple use case, I want to authenticate using passport and if the user is authenticated,...

Hi I followed examples/basic-starter-api-gateway-v1 setup and updated app.js to include a new endpoint definition that uses fetch to call an external end point , external rest endpoint implemented within express...

Could you please provide some example how to handle records n+1 size? For example I need to handle stream of events form SNS. ```js exports.handler = async (event, context) =>...

First of all thank you so much for your great work and effort in maintaining this library. I'm very happy you have added an integration and unit test to the...

docs

Could you please add a TypeScript export for the `setCurrentInvoke` function? [current-invoke.d.ts](https://github.com/vendia/serverless-express/blob/mainline/src/current-invoke.d.ts) only exposes `getCurrentInvoke`. This is needed to set event and context when debugging locally using `app.local.ts`