middy
Advanced tools
Comparing version 0.28.2 to 0.28.3
{ | ||
"name": "middy", | ||
"version": "0.28.2", | ||
"version": "0.28.3", | ||
"description": "🛵 The stylish Node.js middleware engine for AWS Lambda", | ||
@@ -5,0 +5,0 @@ "main": "./index.js", |
@@ -51,2 +51,3 @@ <div align="center"> | ||
- [Typescript](#typescript) | ||
- [FAQ](#faq) | ||
- [3rd party middlewares](#3rd-party-middlewares) | ||
@@ -656,3 +657,10 @@ - [Contributing](#contributing) | ||
## FAQ | ||
### Q: Lambda timing out | ||
**A**: If Lambda is timing out even though you are invoking a callback, there may still be some events in an event loop that are | ||
preventing a Lambda to exit. This is common when using ORM to connect to the Database, which may keep connections to the database | ||
alive. To solve this issue, you can use `doNotWaitForEmptyEventLoop` middleware, which will force Lambda to exit when you invoke | ||
a callback. | ||
## 3rd party middlewares | ||
@@ -678,3 +686,2 @@ | ||
## Contributing | ||
@@ -681,0 +688,0 @@ |
184877
696