-
Notifications
You must be signed in to change notification settings - Fork 672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with AWS API Gateway #662
Comments
Thanks for the report! I'll take a look and update you. |
Same problem here, I solved it using serverless-http. |
Did this only just start happening? Is it only an issue when using Swagger UI? |
I had never used serverless-express with swagger-ui-express and API Gateway but when I tried it (monday) I had this problem with the blank screen on the swagger route. |
If you use AWS Lambda function URLs with Vendia's serverless-express package works pretty fine with Swagger but if use with AWS API Gateway It returns a blank screen on the doc page. |
Related to #400? |
No, it's not! |
I already got an error like this and it was caused by low lambda concurrency, below 5 the Swagger will not render, maybe is not related but try to check the concurrency. |
Vendia's
serverless-express
package does not work as expected with AWS API Gateway, it only returns a blank screen instead the swagger screen.This issue is forcing us to use the
serverless-http
package.To reproduce the error, you basically have to:
*Node versions tried: 14/16/18/20
BTW. Using AWS Lambda function URLs Vendia's
serverless-express
package works pretty fine with swagger.Example of a simple project containing express, serverless-http or vendia and swagger:
The text was updated successfully, but these errors were encountered: