Version 8 [Draft]

[willfarrell]

Version 8

• Drop Node v22, Add support fro Node v24

  • Update engines to "node": ">=24"
  • Update GitHub Actions workflows node-version
  • update "@types/node": "^24.0.0"
  • update @tsconfig/node24
  • update GitHub ruleset for main

• docs

  • Add docs/upgrade/7-8.md
  • update docs/intro/09-release cycle.md

• 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)

• Deprecate Report-To, default to Reporting-Endpoints (NEL still requires Report-To)

• Drop references to callback in core ([FEEDBACK REQUEST] Should AWS Lambda deprecate callback-style function handlers for Node.js 24 and later? aws/aws-lambda-nodejs-runtime-interface-client#137)

• Deprecate @middy/do-not-wait-for-empty-event-loop. context.callbackWaitsForEmptyEventLoop and context.lambdaContext.callbackWaitsForEmptyEventLoop will no longer be used. (Deprecate context.callbackWaitsForEmptyEventLoop? aws/aws-lambda-nodejs-runtime-interface-client#177)

• node26 runtime (Lambda managed runtime for Node.js 26 aws/aws-lambda-roadmap#56)

• http-error-handler all logger access to request

• Update middleware that need access to before context to use a new pattern

  • Use the package name as the key within a middy context
  • { ...request.context, middy: { 'pkg':{} }
  • s3-object-response
  • http-content-negotiation

• replace default console.{log,warn,error} loggers for no-op or false

  • input-output-logger
  • util

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