v2.4.2

• Do not return result of inner handler for lambda #637
  • As of this release, the lambdaHandler no longer supports the non-callback version of lambda functions which have been deprecated by AWS for a while (https://docs.aws.amazon.com/lambda/latest/dg/programming-model.html). This is to fix a bug when returning values from handlers for version 8.10. If you are using Lambda, you should be on Node v6.10 or higher and using the callback parameter for communication with the runtime. The change to using the callback versions the inline return is trivial (return x becomes callback(null, x))
• Report lambda timeouts 1 second before they happen #634
  • Introduce the option captureLambdaTimeouts which defaults to true. When this is true we will install a watchdog that will attempt to notify Rollbar of a timeout 1s before the context would expire. Alternatively, if you pass a second function to lambdaHandler we will invoke that function 1s before the timeout instead of our own which will allow you to do whatever you might want to right before a timeout.
• Handle Symbols in formatArgsAsString #635
• Ignore last error for real #633
• Be super extra careful about accessing exception properties #632
• Use curry provided by Prototype if it exists #631
• Do not throw on bad input to parseUri #628
• Create a utility for truncation, use it on telemetry log messages #630
  • We now will attempt to truncate payloads that would have resulted in a 413
• Scrub values of some known DOM elements #627
  • We include more default keys for scrubbing in the browser as well as default to scrubbing input fields in telemetry items where the name matches anything in the scrub fields if a custom telemetryScrubber function is not defined.