Version 5

[willfarrell]

aka "The ESM Only Update"

Alpha: May/June (after initial nodejs release)
Beta: Sept/Oct
Release: Nov (after nodejs active LTS starts)

• Timelines based on AWS nodejs20.x release cycle

Planned

• Drop Node v16, Add support fro Node v20 (Node v20 Released aws/aws-lambda-base-images#91)
  • Update engines to "node": ">=18"
  • Update github workflows node-version
  • Update swc to use es2022 (https://github.com/tsconfig/bases/tree/main/bases)
• Drop CJS support, ESM only (do last, touch base with Powertools team before, they still use cjs)
• TypeScript Update TypeScript improvements - what should we address? #1023
• event-normalizer: review for any new events from AWS docs and event list
• http-security-headers: review against helmet, MDN, ASVS
• Update all custom error messages to follow same error pattern. {cause:{package:'@middy/*****', ...}}
• http-multipart-body-parser change disableContentTypeError to false by default
• http-urlencoded-body-parser change disableContentTypeError to false by default
• http-json-body-parser change disableContentTypeError to false by default
• http-cors change disableBeforePreflightResponse to false by default
• s3-object-response update to use fetch over https
  • X-Ray doesn't support fetch
• ws-json-body-parser deprecate rawBody from event
• store preferred* in context instead of event for http-content-negotiation
• error-logger pass in context with request.error

Polyfills

>= 17

• replace deep clone hack for structuredClone
  • input-output-logger
• Update how Abort timeout works in core (https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal/timeout) - No, prevent use to manual abort which is useful.

>= 18

• update to use fetch over https

>= 19

>= 20

New Middleware?

• kms - download public key(s) - Nah
• stream - apply streams to key path - Nah
• sfn-large payload Save and load Lambda result payload to S3 #1066 - Nah

Maybe

• benchmarking (can be done after release)
• switch to esbuild? Nah, dropping CJS
• Move to Otel for Logs, Metrics, Traces? End of support for X-Ray SDK?  aws/aws-xray-sdk-node#515
  • Update Logs, Metrics, Traces to use OTel if ready (https://github.com/willfarrell/aws-wishlist#lambda)
  • Use Otel: https://aws-otel.github.io/docs/getting-started/javascript-sdk
  • Use powertools: https://awslabs.github.io/aws-lambda-powertools-typescript/latest/core/tracer/#patching-aws-sdk-clients
  • discussion: AWS Distro for OpenTelemetry aws-powertools/powertools-lambda-typescript#665
• error-logger update to print otel by default
• input-output-logger update to print in otel format
• deprecate use of qs in http-urlencode-body-parser for URLSearchParams. No, doesn't support nested objects though

Next Version

• Update abort signals if Lambda adds support
• Routers updated to support URLPattern? No, still experimental
• http-urlencode-body-parser rename to http-urlencoded-body-parser? Nah

[KillDozerX2]

Either you're moving too fast to I'm too slow. I just switched to node16 today and saw this.
Anyways, keep up the good work guys!

[willfarrell]

@KillDozerX2 lol, neither. AWS released two nodejs runtimes this year, nodejs16.x later than expected and nodejs18 way earlier than expected. I'm hopeful we'll get nodejs20.x by late fall next year. We follow the runtime release cycle for major releases, so lots of time till the next version. I create a draft of the next release to capture everything that didn't make it into the current release so it doesn't get lost.

[dave-irvine]

Can I 👎 on Drop CJS support, ESM only?.

I cannot describe the pain I have gone through trying to use node-fetch in ESM-only mode, I had to drop down to their previous major release. I cannot make ESM-only work with esbuild no matter what I try.

node-fetch/node-fetch#1263 describes a litany of issues people are facing.

Just my 2 cents, I can understand wanting to move forward.

[willfarrell]

Thanks for the feedback. It's just an idea right now. FYI fetch is built into NodeJS 18, finally no more polyfill is needed.

This is the esbuild script I use, if you'd like to give it a try:

node_modules/.bin/esbuild ${1} \
		--platform=node --format=esm  --target=node18 --bundle --minify \
		--banner:js="import { createRequire } from 'module';const require = (m) => { if (m === './reserved.js') return {}; return createRequire(import.meta.url)(m);};const __dirname='.';" \
		--legal-comments=external --sourcemap=external \
		--allow-overwrite --outfile=${1%.js}.mjs

[olanb7]

Integration with aws-lambda-powertools would be a nice add. It's not much, but we're currently enriching the logger in middleware:

export const LoggerMiddleware = (logger: Logger): middy.MiddlewareObj => {

  const before: middy.MiddlewareFn = async (request: middy.Request): Promise<void> => {
    logger.addContext(request.context);
    logger.addPersistentLogAttributes({
      service: request.context.functionName,
      ...getIdentityAttributes(request),
    });
    
    ...

[willfarrell]

@olanb7 Powertool already has a Middy middleware for their logger. See https://awslabs.github.io/aws-lambda-powertools-typescript/latest/core/logger/#capturing-lambda-context-info, might be of use to you.

[willfarrell]

5.0.0-rc.0 is now released.