middy
middy copied to clipboard
Version 7 [Draft]
aka The OTel Update (Hopefully)
Release: Nov (after nodejs active LTS starts)
Timeline based on AWS nodejs24.x release cycle
Release Notes: https://github.com/middyjs/middy/blob/release/7.0.0/website/docs/upgrade/6-7.md
Planned
-
[x] Drop Node v20, Add support fro Node v24
- [x] Update
enginesto"node": ">=22" - [x] Update github workflows
node-version - [x] update
"@types/node": "^22.0.0" - [x] update
@tsconfig/node22 - [x] update
@tsconfig - [x] update GitHub ruleset for
main
- [x] Update
-
[x] docs
- [x] Add
docs/upgrade/6-7.md - [x] update
docs/intro/09-release cycle.md
- [x] Add
-
[ ] OTLP Support #1520
-
[ ] LLRT Support #1181
Version 8
- [ ] Use new RegExp.escape function in routers (https://nodejs.org/en/blog/release/v24.0.0)
- [ ] Use new URLPattern function in routers (https://nodejs.org/en/blog/release/v24.0.0)
- [ ] Drop references to callback in
core(https://github.com/aws/aws-lambda-nodejs-runtime-interface-client/issues/137) - [ ] Deprecate
Report-To, default toReporting-Endpoints(NEL still requires Report-To)
Maybe
- [ ] improve response streaming support (new middlewares?)
- [ ] plugins as packages?
- [ ] Move to JSDoc notation? https://www.youtube.com/watch?v=zPOHY-cZ1wE
- [ ] Update abort signals if Lambda adds support
Update on the release of v7. Due to some major changes to lambda announced at re:invent, v7 will be delayed to allow time to understand what the new best practices are and how best they should be introduced into middy.
If you have thoughts on how middy should handle the new tenant isolation, managed instances, or the new context handling, please comment.