@orikami/micro-to-lambda - npm Package Compare versions

Comparing version 1.1.0-rc1 to 1.2.1

index.js

		@@ -68,3 +68,3 @@ var Stream = require('stream');
		callback(new Error("Did not promise to close database connection"))
		process.exit();
		return
		}
		@@ -78,13 +78,7 @@
		callback(null,res.toLambdaResponse())
		if (!keepAlive) {
		process.exit();
		}
		})
		.catch(err => {
		callback(err);
		if(!keepAlive) {
		process.exit()
		}
		});
		}
		}

package.json

README.md

		@@ -25,7 +25,20 @@ # micro-to-lambda

		If you're using `async` or `await` syntax, it is recommended to use the
		`async-to-gen` helper to make code compatible for node 6.10.x
		By default, the lambda will terminate the process after every request.
		If you want to keep the process alive, use:

		```
		microToLambda(handler, { keepAlive: true, iPromiseToCloseDatabaseConnections: true })
		```

		As you can see, you have to promise to close all database connections (to MongoDB). Otherwise, the autoscaling of lambda can cause trouble for the connection limit of the database.


		```javascript
		require("async-to-gen/register");
		```

		## Changelog

		1.2.0 - Remove process.exit() to fix error.
		1.1.1 - Close AWS Lambda after every process. (HAS ERRORS)
		0.0.01 - Initial release

New alerts