Skip to content

v3.0.0
Compare
Choose a tag to compare
@github-actions github-actions released this 12 Apr 15:21
· 102 commits to master since this release
v3.0.0
1ba3e4d

3.0.0 (2021-04-12)

Bug Fixes

  • add .npmignore file to help reduce the size of the package (c21bd7f)
  • do not use husky when on a CI environment (a17ac76)
  • reverse the check for LAMBDALOG_SILENT env variable (95828b1)

Code Refactoring

  • move message.tags to a getter and setter (201a6fe)

Features

  • add ability for tags to be functions (459380f)
  • add ability to change the key names of the message output (4a71909)
  • add new method addLevel() to LambdaLog (9fde2e3)
  • add new options levelKey, messageKey, and tagsKey (bb5ba70)
  • add new website! (44a15dc)
  • add symbols to reference certain private properties on LogMessage class (952b62d)
  • convert Errors in metadata to plain objects #31 (576052a)
  • remove default tags and add tag variable support #29 (ae686ef)
  • set node engine to >= 10.0.0 (2d022ec)
  • switch from travis to github actions (f2d418e)
  • use jest for testing and coverage (fafed5d)
  • internal: add function to stub errors with a toJSON method (d0707bd)

BREAKING CHANGES

  • There are no longer any built-in tags added to the tags array for each log message.
  • message.tags is no longer a property of the LogMessage class that can be directly changed.
  • Whenever an Error object is passed into the metadata for a log message, it will automatically be converted to a plain object as stringifying the an Error object will always yield {}.
  • Previously you could directly access the private properties of LogMessage. In order to add some integrity, they are no longer using standard property names starting with an underscore and are instead referenced using symbols instead. For advanced usage, these symbols are exported as a static property on the LogMessage class under LogMessage.symbols.
  • Previously you could directly access the private properties of LambdaLog. In order to add some integrity, they are no longer using standard property names starting with an underscore and are instead referenced using symbols instead. For advanced usage, these symbols are exported as a static property on the LambdaLog class under LambdaLog.symbols.
Assets 2
Loading