serverless-express
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.
`@vendia/[email protected]` ```typescript app.post('/webhook', async (req, res) => { const { event, context } = getCurrentInvoke() console.log(util.inspect({ event, req }, false, null)) } // event.headers['content-type] = "420" // req.headers['content-type] = 420...
Using version `@vendia/serverless-express`: **4.5.2** Trying to import the "serverlessExpress" module and do something similar as described here: https://github.com/vendia/serverless-express/blob/mainline/examples/basic-starter-api-gateway-v2/src/lambda-async-setup.js but, in a TypeScript project. ```ts import logger from 'src/logger'; import ConfigurationProvider...
We are using vendia aws serverless express package for running the angular app in ssr mode using express to be served from serverless. We upgraded from 3.x to 4.x Handler...
AWS always includes the stage name in the request path of API Gateway V2 events, even when using a custom domain and an ApiMapping. **Without a custom domain** * Invoke...
### app.post("/path/path", (req, res) => { } I am not sure what exactly is the issue is, but it seems that my **req** variable contains weird data from aws- api...
**Context:** upgrading from 3.3.8 to 4.3.11. `headers` is always replaced by `multiValueHeaders` : https://github.com/vendia/serverless-express/blob/6adac653fe1daf1dd44ff6aa17dbf08f07662173/src/event-sources/aws/alb.js#L40-L54 But according to https://docs.aws.amazon.com/elasticloadbalancing/latest/application/lambda-functions.html#multi-value-headers, it should only happen when the multi-value headers feature is enabled on...
req.path is set like below. ``` 1. https://domain/test => req.path = '/test' 2. https://domain/test/ => req.path = '/test' ``` 2 is not correct, since Express actually set '/test/' to path...
They use APIGatewayProxyEvent. "errorMessage":"Unable to determine event source based on event." Not sure why this isn't detected.
### Description I think there exists a timing problem between sending the HTTP response passed to express and promise rejections happening afterwards. See this pseudo code: ``` app.get('/', async (req,...
I've created an example that uses `vendia/serverless-express` with Typescript in the examples directory Please have a look at this PR https://github.com/vendia/serverless-express/pull/453