-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@aws-sdk/client-sesv2 - Error: Cannot find module '@aws-sdk/util-endpoints' #4053
Comments
Same issue with |
I got the same error.
|
Hi guys, same here. Should you need anything to help diagnose, just ask. Keep up the good work! Cheers, |
Version 3.192.0 released today and is busted, so until aws/aws-sdk-js-v3#4053 is fixed, we're locking down to lower versions to fix CI
Acknowledged that this is a bug. It can be temporarily fixed by adding
Another option is to pin client version to
We'll attempt to push fix in |
In our project we use Pin dependencie version to "dependencies": {
+ "@aws-sdk/client-s3": "3.188.0"
- "@aws-sdk/client-s3": "^3.188.0"
} |
This happens as
However, it's not added as a dependency in package.json aws-sdk-js-v3/clients/client-sesv2/package.json Lines 19 to 55 in 87fc297
The fix in the SDK would be similar to what's done by @JagWireZ in #4055, but it would be codegen. |
The issue is in EndpointsV2Generator.java which adds |
Fixes are ready: |
This issue is fixed in Source codeimport { SESv2 } from "@aws-sdk/client-sesv2";
const client = new SESv2({});
console.log(await client.listConfigurationSets({})); Cannot find module error with @aws-sdk/client-sesv2@3.192.0node:internal/modules/cjs/loader:985
const err = new Error(message);
^
Error: Cannot find module '@aws-sdk/util-endpoints'
Require stack:
- /Users/trivikr/workspace/test/node_modules/@aws-sdk/client-sesv2/dist-cjs/endpoint/endpointResolver.js
- /Users/trivikr/workspace/test/node_modules/@aws-sdk/client-sesv2/dist-cjs/runtimeConfig.shared.js
- /Users/trivikr/workspace/test/node_modules/@aws-sdk/client-sesv2/dist-cjs/runtimeConfig.js
- /Users/trivikr/workspace/test/node_modules/@aws-sdk/client-sesv2/dist-cjs/SESv2Client.js
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:985:15)
at Function.Module._load (node:internal/modules/cjs/loader:833:27)
at Module.require (node:internal/modules/cjs/loader:1057:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object.<anonymous> (/Users/trivikr/workspace/test/node_modules/@aws-sdk/client-sesv2/dist-cjs/endpoint/endpointResolver.js:4:26)
at Module._compile (node:internal/modules/cjs/loader:1155:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
at Module.load (node:internal/modules/cjs/loader:1033:32)
at Function.Module._load (node:internal/modules/cjs/loader:868:12)
at Module.require (node:internal/modules/cjs/loader:1057:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/Users/trivikr/workspace/test/node_modules/@aws-sdk/client-sesv2/dist-cjs/endpoint/endpointResolver.js',
'/Users/trivikr/workspace/test/node_modules/@aws-sdk/client-sesv2/dist-cjs/runtimeConfig.shared.js',
'/Users/trivikr/workspace/test/node_modules/@aws-sdk/client-sesv2/dist-cjs/runtimeConfig.js',
'/Users/trivikr/workspace/test/node_modules/@aws-sdk/client-sesv2/dist-cjs/SESv2Client.js'
]
} No error with @aws-sdk/client-sesv2@3.193.0{
'$metadata': {
// Redacted
},
ConfigurationSets: []
} |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Checkboxes for prior research
Describe the bug
After upgrading @aws-sdk/client-sesv2 to version 3.191.0
Got a message
Cannot find module '@aws-sdk/util-endpoints'
@aws-sdk/client-sesv2@3.191.0 history link
SDK version number
@aws-sdk/client-sesv2@3.191.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
node.js 14.16.0
Reproduction Steps
Observed Behavior
Expected Behavior
No errors at run time.
Possible Solution
No response
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered: