Node.js: module not found using ES import with Lambda layers

1

We're trying to deploy a Lambda function with AWS SDK v3 modules. The imports are standard ES syntax and work fine in a local setup, and work if we package the entire module into the function:

import { SESv2Client, SendEmailCommand } from '@aws-sdk/client-sesv2';

For efficiency and reuse, we moved the modules into a layer. When we run the function (tried with Node.js 14 and 16 runtimes), we continue to receive:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@aws-sdk/client-sesv2' imported from /var/task/index.js

If we strip out the ES pieces and use CommonJS syntax with require statements, the modules load correctly. Obviously we would prefer the modern syntax and the performance gains that go with it. According to AWS docs, node.js lambda functions support ES imports in Node.js 14.x and Node.js 16.x.

Has anyone else run into this and found a solution?

已提問 2 年前檢視次數 3679 次
2 個答案
0
已接受的答案

Unfortunately AWS support has confirmed we can't utilize layers with ES:

importing ESM modules from layers seems to not be supported when using a module type in Lambda. [...] this is a Node feature blocking us to import ES modules from a layer as "NODE_PATH" variable is not supported by the ESM loader in node

Disappointing that AWS is making headway on supporting ES, but it means we lose the functionality of layers. Support provided a wrapper workaround that we'll be trying. It corresponds with what we found here. Hopefully this saves someone else the headache we've gone through the last week.

已回答 2 年前
profile picture
專家
已審閱 6 個月前
0

Is this still the case with node18.x???

已回答 1 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南