Error with Lambda Layers: Class extends value undefined is not a constructor or null

[defish1962]

I am using Lambda Layers with my Amplify project. I recently upgraded from AWS SDK v2 to v3 and am now experiencing some runtime errors in my Lambda functions that utilize Lambda Layers.

I have a Lambda Layer that is used to make AppSync queries and mutations. When that layer is used in a Lambda function, the following error is thrown when the Lambda function tries to load:

{
"errorType": "Runtime.UnhandledPromiseRejection",
"errorMessage": "TypeError: Class extends value undefined is not a constructor or null",
"reason": {
"errorType": "TypeError",
"errorMessage": "Class extends value undefined is not a constructor or null",
"stack": [
"TypeError: Class extends value undefined is not a constructor or null",
" at Object. (/opt/nodejs/node_modules/@aws-sdk/client-sso/dist-cjs/SSOClient.js:17:41)",
" at Module._compile (node:internal/modules/cjs/loader:1256:14)",
" at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)",
" at Module.load (node:internal/modules/cjs/loader:1119:32)",
" at Module._load (node:internal/modules/cjs/loader:960:12)",
" at Module.require (node:internal/modules/cjs/loader:1143:19)",
" at require (node:internal/modules/cjs/helpers:119:18)",
" at Object. (/opt/nodejs/node_modules/@aws-sdk/client-sso/dist-cjs/index.js:5:22)",
" at Module._compile (node:internal/modules/cjs/loader:1256:14)",
" at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)"
]
},
"promise": {},
"stack": [
"Runtime.UnhandledPromiseRejection: TypeError: Class extends value undefined is not a constructor or null",
" at process. (file:///var/runtime/index.mjs:1276:17)",
" at process.emit (node:events:517:28)",
" at emit (node:internal/process/promises:149:20)",
" at processPromiseRejections (node:internal/process/promises:283:27)",
" at process.processTicksAndRejections (node:internal/process/task_queues:96:32)"
]
}

Here is my package.json file for the Lambda Layer:

{
"version": "1.0.0",
"description": "Lambda Layer to run a GraphQL query - refLambda",
"type": "module",
"main": "index.js",
"dependencies": {
"@aws-crypto/sha256-js": "^2.0.1",
"@aws-sdk/credential-provider-node": "^3.76.0",
"@aws-sdk/protocol-http": "^3.58.0",
"@aws-sdk/signature-v4": "^3.58.0"
},
"devDependencies": {}
}

What is strange is that not all of the Lambda functions that use this layer generate this error. I can't identify what is different between the ones that work and the ones that do not.

Here is the package.json file for a Lambda function that doesn't work:

{
"name": "testlayers",
"version": "2.0.0",
"type": "module",
"description": "Lambda function generated by Amplify",
"main": "index.js",
"license": "Apache-2.0",
"devDependencies": {
"@types/aws-lambda": "^8.10.92"
}
}

And here is the package.json file for a function that does work:

{
"name": "checkinvitationstatus",
"version": "2.0.0",
"type": "module",
"description": "Lambda function generated by Amplify",
"main": "index.js",
"license": "Apache-2.0",
"dependencies": {},
"devDependencies": {}
}

Any suggestions on what might be causing this error would be greatly appreciated. My research has come up with the possibility that it could be circular dependency references or incompatible packages but I cant identify either of those issues in the code.

Thanks.

[defish1962]

It turns out the error was caused by the merge order of the Lambda Layers. Once I changed the order on the Lambda functions that were failing they started working again. Very difficult issue to track down!

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.