now throws error if config has a JSON error

Previously JSON errors in the config file were passed over in silence, leading to all kinds of confusion.
If the config file exists and has no error, this will run as normal.
If the config file does not exist, this will run as normal.
If the config file exists but has an error in it, this will throw the error and crash.

handle when not base64

response.js fixes an error that occurs if 'body' is not base64-encoded

allow API Version 2.0

See https://aws.amazon.com/blogs/compute/building-better-apis-http-apis-now-generally-available/ for details

fix CORS error when res does not have headers

7.4.1

7.4.1

allow global options

You can now set options for all routes by putting them inside a 'response: {...}' field in the conf file.

CORS support

{ cors: true } in the config will allow cross-origin requests and preflight checks for GET/POST/PUT/DELETE.

middleware before and after

Now supports 'before' and 'after' middleware methods for additional processing, see test.middleware.js for examples.

fixes incorrect redirect with '/', fixes tests

7.0.1

patch not minor

normalize headers and body

This will now force all incoming headers to be all lowercase, so response functions that assumed they were in some capitalized format need to be updated. This also now passes application/json bodies as a JS object rather than as a base-64 JSON string.

logger method

Now logs to console.error if tag level is 'ERROR', this way AWS logging recognizes the log as an error log.