v2.4.5

Release v2.4.5

v2.4.4

• Pass original item to transform as second param

v2.4.3

• Fix the way rejected promise reasons are turned into strings #651
• Make the rate limiter a little more resilient #649
• If you set an onerror handler before Rollbar loads, we should be calling it even though we set our own, this fixes a bug where that did not always happen #645
• Further fix for prototypejs users #639

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.

v2.4.1

• Fix the way options are merged: #617
• Support code_version and codeVersion at the top level of the configuration to alleviate some ambiguity: #618
• Add types for the express error handler: #619

v2.4.0

• Introduce the captureIp configuration settting.
  For browser settings, this determines how we attempt to capture IP addresses from the client
  that submits items. For server settings, this determines how we capture IP addresses from requests.

  Possible values are: true, false, or anonymize.

  If true then we will attempt to capture and store the full IP address of the client.
  If set to anonymize we will do a semi-anonymization on the captured IP address by masking out
  the least significant bits.
  If set to false we will not attempt to capture any IP address.

  Default: true

• Introduce the captureUsername and captureEmail configuration settings.
  In the server context, as described in the documentation, we attempt to gather information about
  the current user. Prior to this release, we tried to gather the id, username, and email.
  Starting with this release, by default we only attempt to capture the id for a user.
  The boolean configuration options captureEmail and captureUsername can be used to change
  this behaviour.

v2.3.7

• Fix some React Native related issues

v2.3.5

Release v2.3.5

v2.3.2

• Be defensive about navigator not existing on window
  #514

• Proper scrubbing
  #510

• Be defensive when accessing event properties
  #503

• Add environment to options type enhancement
  #499

• call the transform in the options on the server side too
  #498

• fixes errMsg.match is not a function error
  #492

• Call callback even if logging same as last error
  #490

v2.3.1

CDNJS is being wonky, attempt to fix by bumping the release version.