You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the latest llrt-lambda-arm64.zip layer bundle on some of my Lambda functions are working great.
Now I have a use case where I need to have comprehend, translate or polly modules. What I did was bundle those packages into my code. I first got an error that @smithy/shared-ini-file-loader module was not found. So I added that module to the code but now I'm getting Error resolving module url.
My Lambda function also uses DynamoDB. When I removed all references to comprehend or translate it worked perfectly. But adding comprehend, translate or polly breaks it.
Its complaining in this line of code in my Lambda function.
Any ideas on how to fix that?
Running on Node 18
The text was updated successfully, but these errors were encountered:
jagonzalr
changed the title
Error resolving module url when bundling @aws-sdk/client-comprehend or @aws-sdk/client-translate
Error resolving module url when bundling @aws-sdk/client-comprehend, @aws-sdk/client-translate or @aws-sdk/client-polly
Mar 13, 2024
URL module is WIP. Should be there quite soon. Please target browser when bundling SDKs that are not already embedded :) That should help with some issues. I'll also add an example how to add a SDK client that is not already bundled.
See: #214
Hello,
Using the latest llrt-lambda-arm64.zip layer bundle on some of my Lambda functions are working great.
Now I have a use case where I need to have comprehend, translate or polly modules. What I did was bundle those packages into my code. I first got an error that
@smithy/shared-ini-file-loader
module was not found. So I added that module to the code but now I'm gettingError resolving module url
.My Lambda function also uses DynamoDB. When I removed all references to comprehend or translate it worked perfectly. But adding comprehend, translate or polly breaks it.
Its complaining in this line of code in my Lambda function.
Any ideas on how to fix that?
Running on Node 18
The text was updated successfully, but these errors were encountered: