fix(maintenance): remove upper peer dependency Middy #1705
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of your changes
This PR removes the upper bound of the peer dependency on Middy that was introduced in the latest release.
As described in the linked issue, Powertools for AWS (TypeScript) is officially compatible only with Middy 3.x. This is documented both our documentation(see callout titled "A note about Middy") as well as Middy's documentation (here).
This is due to Middy's release cycle that favors more recent Node.js versions, which is not compatible with our current release cycle which instead is aligned with Node.js versions supported by AWS Lambda.
After making the release however, several members of the community have reached out informing us that this new strict peer dependency breaks their builds. While it's possible to circumvent the peer dependency constraint using npm's
--force
flag, we recognize that this doesn't constitute a good experience and so we are rolling back the change and relaxing the peer dependency constraint.We'll revisit the topic in our upcoming major release.
Related issues, RFCs
Issue number: #1702
Checklist
Breaking change checklist
Is it a breaking change?: NO
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.