v2.2.2

• Default charset=utf-8 for serializer mime-types. This fixes requests with the charset set in the Accept header, eg: Accept: application/json; charset=utf-8.

v2.2.1

• Default instance in RestEvent.validateBody error messages to requestBody. Value can still be overridden.

v2.2.0

• Added the ProxyEvent and Lambda context to the parameters passed to the error handler.

v2.1.0

• Added support for Node v8.10 which requires results returned in a Promise.

Support for v4.3 and v6.10 will continue until it is no longer possible to update code on Lambda Functions configured for those runtimes.

v2.0.1

• Fixed unparsable application/json request bodies resulting in an HTTP 500 response (they now result in a 400).

v2.0.0

• Added RouteBuilder.serializers which allows endpoints to support multiple response mime types. See the new section in the README for an explanation.
• String responses with Content-Type set to application/json will no longer have JSON.toString called again as this is a possible double-serialization. This is technically a breaking change so it's time for 2.0.
• Removed deprecated RouterEvent.whitelistStringQueryParameters(). Use whitelistQueryStringParameters() instead.
• Changed RouterEvent._headersLowerCase to RouterEvent.headersLowerCase for consistency with Node.
• Removed RouterEvent.getHeader().
• Added fileExtensionBlacklist option to FileSystemRoute.

v1.7.0

• Added RouterEvent.validateBody() to validate the request body using JSON Schema.

v1.6.0

• Added ProxyRoute for easy proxying of requests to another server.
• Added fileExtensionWhitelist config option to FileSystemRoute.

v1.5.1

• Fix URL parsing on versions of node < v6.13.0.

v1.5.0

• Normalize incoming paths. eg: /foo/bar/../baz should resolve to /foo/baz.