claudia-api-builder - npm Package Compare versions

Comparing version 1.5.0 to 1.5.1

package.json

 {
   "name": "claudia-api-builder",
-  "version": "1.5.0",
+  "version": "1.5.1",
   "description": "Simplify AWS ApiGateway handling",
@@ -5,0 +5,0 @@ "license": "MIT",

README.md

@@ -35,3 +35,3 @@ #Claudia API Builder
 
-* Check out the [Getting Started](docs/getting_started.md) guide for a basic Hello-World style example
+* Check out the [Getting Started](https://claudiajs.com/tutorials/hello-world-api-gateway.html) guide for a basic Hello-World style example
 * Check out the [API Documentation](docs/api.md) for a detailed guide on handling requests, customising responses and configuring your API
@@ -38,0 +38,0 @@

RELEASES.md

 # Release history
 
+## 1.5.1, 4 August 2016
+
+- by default, API processing stops the node VM using the [callbackWaitsForEmptyEventLoop](http://docs.aws.amazon.com/lambda/latest/dg/nodejs-prog-model-context.html) Lambda context parameter. This is to prevent runaway node.js events caused by third party libs causing the Lambda VM to become stuck after a request completes. If you really want the VM execution to continue until the event loop empties, even after your API process is done, then set `lambdaContext.callbackWaitsForEmptyEventLoop` to `true` in your request handler.
+
 ## 1.5.0, 12 July 2016
@@ -4,0 +8,0 @@

src/api-builder.js

@@ -44,2 +44,3 @@ /*global module, require */
 			var handler, result, path;
+			context.callbackWaitsForEmptyEventLoop = false;
 			if (event && event.context && event.context.path && event.context.method) {
@@ -46,0 +47,0 @@ path = event.context.path;

No alert changes

Improved metrics

Total package byte prevSize

11953

increased by5.71%

Lines of code

239

increased by0.42%

No dependency changes