Lambda API: v0.5 Released

Lambda API v0.5 is here! There have been some exciting changes in the AWS serverless ecosystem in the last few months, but most importantly, support for Node v8.10! That means we can now use async/await instead of promises. This news prompted a rewrite of the core execution process to take advantage of the simplicity of async/await. This greatly simplified the code, removed the dependency on Bluebird, and made Lambda API even faster! Like sub-millisecond faster! 🏎

In addition to removing the Bluebird dependency, v0.5 adds a number of features to help solve additional use cases and speed up serverless development workflows. New built-in CORS support makes it easy to add default CORS headers with a single method call. Additional wildcard features have been added that allow specifying wildcards on nested routes, giving you more control over responding to OPTIONS requests. Several HTTP header management methods have been added including hasHeader(), getHeader(), and removeHeader(), as well as standardizing response header case to make management easier and comply with HTTP/2 standards.

Progress was also made on supporting additional standards such as HEAD requests. An alias was added to HEAD requests that will automatically match them to existing GET routes. This will then execute the route and return the headers without a body. There is more to be done here, but this is a step closer to meeting all the standards.

Lambda API's goal is to be a full-featured, lightweight web framework for your serverless applications. ⚡ If you have any feature requests, use case ideas, or other comments, please send me a message or post an issue on GitHub.

NPM: https://www.npmjs.com/package/lambda-api

GitHub: https://github.com/jeremydaly/lambda-api

Built-In CORS Support

A convenience method named cors() is now available for adding CORS headers to responses. An optional options object can be passed in to customize the defaults.

The six defined CORS headers are as follows:

Access-Control-Allow-Origin (defaults to *)
Access-Control-Allow-Methods (defaults to GET, PUT, POST, DELETE, OPTIONS)
Access-Control-Allow-Headers (defaults to Content-Type, Authorization, Content-Length, X-Requested-With)
Access-Control-Expose-Headers
Access-Control-Max-Age
Access-Control-Allow-Credentials

The options object can contain the following properties that correspond to the above headers:

origin (string)
methods (string)
headers (string)
exposeHeaders (string)
maxAge (number in milliseconds)
credentials (boolean)

Defaults can be set by calling res.cors() with no properties, or with any combination of the above options.

javascript
res.cors({
  origin: 'example.com',
  methods: 'GET, POST, OPTIONS',
  headers: 'Content-Type, Authorization',
  maxAge: 84000000
})

You can override existing values by calling res.cors() with just the updated values:

javascript
res.cors({
  origin: 'api.example.com'
})

HTTP Header Management

Three new HTTP header management methods have been added.

getHeader([key])

Retrieve the current header object or pass the optional key parameter and retrieve a specific header value. key is case insensitive.

hasHeader(key)

Returns a boolean indicating the existence of key in the response headers. key is case insensitive.

removeHeader(key)

Removes header matching key from the response headers. key is case insensitive. This method is chainable.

Release Notes:

Feature Release

v0.5 removes Bluebird dependency and adds built-in CORS support, additional wildcard features, new HTTP header management methods and more.

Remove Bluebird Dependency

Close #26 by removing Bluebird promises and replacing processing with async/await a524445
Remove node 6/7 tests in favor of native async/await support 6b9396b
Close #29 by upgrading all tests to async/await 8496285, 0d39e0b