-
Notifications
You must be signed in to change notification settings - Fork 559
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
3.192.0 introduces breaking change: Cannot find module '@aws-sdk/util-endpoints' #4060
Comments
A bit more context:
@thetutlage maybe you want to update the title to something like: "3.192.0 introduces breaking change: Cannot find module '@aws-sdk/util-endpoints'" |
facing same issue, a breaking change for all who are using latest minor versions in package.json I guess. hoping this gets fixed soon. OP - If you could please edit the title to be more precise , It might help with getting right amount of attention asap. |
Facing same issue as well, +1 on getting fixed soon. |
Having the same issue from morning. Hopefully it will be fixed soon. |
Having the same issue as well. |
Same issue |
Getting the same issue with version 3.192.0 |
This easily fixable when going back to 3.190.0. For those that never heard this before: posting "same" doesn't really help contributors. Please provide additional debugging information if possible (although not really needed here). You can also subscribe to the issue and use emoji reactions on the top post to show maintainers the importance of the issue. In case you have "latest" in your package.json: consider using something like Renovate to update your packages. It will create branches with the updated versions, so you will be notified that something broke before having it on your main branches. |
Temporary workaround is to install |
Same issues |
Same issue |
Same here! |
I maked the rollback to version 3.190.0 and works temporarily "@aws-sdk/client-kms": "3.190.0", |
Alternatively, just including the utils module separately works with the latest version of the sdk for example:
|
Same issue |
Así funciono |
#4058 seems to be the fix for it.. waiting for the next release to be fixed, I guess. |
Same issue |
This is what I did to get it working.
|
Yep - broke my app just now with: Fixed it by combing through logs and adding: |
Tried this, it did not work for me |
I experienced the same issue in 734 but the above solutions aren't working for me |
Already fixed, and will be released with Check out details in #4053 |
This issue is fixed in Source codeimport { S3 } from "@aws-sdk/client-s3";
const client = new S3({});
console.log(await client.listBuckets({ Limit: 1 })); Cannot find module error with @aws-sdk/client-s3@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-s3/dist-cjs/endpoint/endpointResolver.js
- /Users/trivikr/workspace/test/node_modules/@aws-sdk/client-s3/dist-cjs/runtimeConfig.shared.js
- /Users/trivikr/workspace/test/node_modules/@aws-sdk/client-s3/dist-cjs/runtimeConfig.js
- /Users/trivikr/workspace/test/node_modules/@aws-sdk/client-s3/dist-cjs/S3Client.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-s3/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-s3/dist-cjs/endpoint/endpointResolver.js',
'/Users/trivikr/workspace/test/node_modules/@aws-sdk/client-s3/dist-cjs/runtimeConfig.shared.js',
'/Users/trivikr/workspace/test/node_modules/@aws-sdk/client-s3/dist-cjs/runtimeConfig.js',
'/Users/trivikr/workspace/test/node_modules/@aws-sdk/client-s3/dist-cjs/S3Client.js'
]
} No error with @aws-sdk/client-s3@3.193.0{
'$metadata': {
// Redacted
},
Buckets: [
// Redacted
],
Owner: {
// Redacted
}
} |
Hi @trivikr thanks for fixing it , but we are still getting these warnings in our builds |
@trivikr I know pretty much everyone ran into this problem with |
I am having the same issue.. any update for bellow error
|
@trivikr
|
./node_modules/@aws-sdk/util-endpoints/dist-es/lib/index.js 1:9
Module parse failed: Unexpected token (1:9)
File was processed with these loaders:
* ./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
> export * as aws from "./aws";
| export * from "./booleanEquals";
| export * from "./getAttr";
2022-10-20T14:02:30.704Z [WARNING]: npm
2022-10-20T14:02:30.704Z [WARNING]: ERR! code ELIFECYCLE
npm ERR! errno 1
2022-10-20T14:02:30.706Z [WARNING]: npm
2022-10-20T14:02:30.706Z [WARNING]: ERR! PEGDashboard@0.1.0 build: "react-scripts build" |
Please follow-up details in #4067 (comment) I suspect the error you're getting is because of the same cause as explained in #4067 (comment) The issue you mentioned if with https://github.com/aws/amazon-chime-sdk-js I'm locking this issue to prevent further noise. The bug discussed in this issue is already fixed and verified in #4060 (comment) |
Checkboxes for prior research
Describe the bug
This commit 6e4371e#diff-2c9b50a7c5201e808afb3f485a693f85389fbeef01b9282a5a31dcd325fffb2aR40 has introduced a breaking change by removing
@aws-sdk/util-endpoints
. However, the module is still in use in this file 6e4371e#diff-6ba586ec001f1ef54aa2387edbec307279cb4e6e815c4af3433dc3eb3fa9a095R3SDK version number
@aws-sdk/client-s3@3.192.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
16.18.0
Reproduction Steps
Just install
@aws-sdk/client-s3@3.192.0
and you will be able to reproduce thisObserved Behavior
Breaks
Expected Behavior
Should not break.
Possible Solution
No response
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered: