In previous builds, if one lambda invocation threw an error, the main "worker" would halt and stop processing SQS messages.
This release fixes that behavior.
Breaking Changes
The module itself will no longer throw an error when a lambda invocation fails.
New Functionality
Provide a postInvoke function for each mapping configuration to handle individual lambda invocation errors in whatever manner you choose.