2.3.0

• #653 prevent error.message from being parsed unnecessarily @CodeVision
• #669 Export TS middy interfaces directly @MelvinVermeer
• #672 Add support to have multiple instances of validator @qualipsolutions
• #675 Add in the ability to log AWS Lambda context in input-output-logger @s1mrankaur

2.2.0

• #667 fix cacheExpiry bug @fdiasr
• #660 Improvement to remove cache when fetch throws error @theburningmonk
• @types/node major version update

2.1.1

• #665 Fix: Response Serializer does not replace entire object when falsey value is returned @roni-frantchi

2.1.0

• #654 bug fix in http-response-serializer where it normalizes the response when there is a 502 error
• #657 regression fix for http-response-serializer
• #658 bug fix unexpected nested mutations in input-output-logger
• bug fix in http-response-serializer where failed to exit when first match found
• bug fix in s3-get-response in edge case 2 body params could be sent
• performance improvements to core, http-urlencode-body-parser, http-response-serializer, http-partial-response, http-content-negotiation, util
• #646 Add new middleware event-normalizer to parse and handle all aws events

2.0.1

• #640 sms bug fix where infinite loop happens when pulling >10 values @garnertb
• #643 improve performance of http-json-body-parser @nponeccop

2.0.0

Checkout UPGRADE.md to see what are the main breaking changes and how to migrate to this new version if coming from 1.x.

Focus this version was on performance and security by default.

Additions

• New middlewares (cloudwatch-metrics, rds-signer, s3-object-response, sts)
• New plugin hook for core to allow easier bottleneck detection with middlewares and handler

Breaking Changes

• All middlewares now use async/await and have deprecated next(err) and callback(err, response)
• validator refactored to support draft-2020-12 using the latest version of ajv (v8). Errors now use instancePath over dataPath. Full i18n is now enabled by default
• http-error-handler no longer exposes status code >= 500 by default.
• Middlewares that reach out to 3rd party API have been completely refactored to have unifying options that resolve on demand from internal context. Applies to:
  • rds-signer
  • secrets-manager
  • ssm
  • sts
• Deprecated middlewares:
  • cache: little usage, makes more sense to be pulled out of core
  • db-manager: little usage, makes more sense to be pulled out of core
  • function-shield: Only supported up to Node v10
  • warmup: AWS now supported reserved provisioned concurrency for Lambda

Maintenance

• Documentation overhaul, with a dedicated section for TypeScript
• Changed test runner to ava/sinon for esm support and keep deps clean
• Added c8 for test coverage logging
• Changed linting to use standard cli to keep deps clean

Thanks to

• @lmammino: For discussions to bounce and talk through ideas. Code audit/review & TypeScript definitions.
• @markcarroll: TypeScript bug fix #630
• @huyennbl: Muti-file parsing support #634
• @ffxsam: For reporting #609.
• @raae & @AyoAlfonso: For expose support in http-error-handler #610.
• @nfantone: For improved response default handling #615
• @fredericbarthelet: For new cloudwater-metrics middleware

2.0.0-beta.1

• mutli-file parsing #634 @huyennbl
• TypeScript fix #630 @markcarroll

2.0.0-beta.0

Add in updated TypeScript support (@lmammino ) and added in a new middleware cloudwatch-metrics (@fredericbarthelet).

2.0.0-alpha.6

Add in http response normalizations and improvement to developer debugging experience. #615 @nfantone

2.0.0-alpha.5

Deprecated onChange option from rds-signer,secrets-manager,ssm,sts (See #611 and #612 for discussion) and modified util.processCache to return flag indicating if it was a cache hit.