-
Notifications
You must be signed in to change notification settings - Fork 672
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
Error [TypeError]: AWS[serviceName] is not a constructor #2085
Comments
I debugged this error and found the codestar plugins to be causing it. I removed those two tests and then this error wasn`t thrown anymore. Nevertheless, the error in this thread started to be thrown: #2059. I hope it helps! Thanks for jumping into these errors! |
Version 3.4.0 runs perfectly if Codestar plugins are removed. As version 3.5.0 included a new plugin for Codestar (CodeStarHasTags) would that one be a candidate for the root cause of this error? |
This crash can be resolved by downgrading |
How do you do that, can you give steps to do it? |
I edited the |
This worked but now another issue started
|
How to fix it? |
Cloned and setup per instructions. First run produced the error below:
Error [TypeError]: AWS[serviceName] is not a constructor
at /home/kali/cloudsploit/collectors/aws/collector.js:139:119
at /home/kali/cloudsploit/node_modules/async/dist/async.js:3113:16
at replenish (/home/kali/cloudsploit/node_modules/async/dist/async.js:1014:17)
at /home/kali/cloudsploit/node_modules/async/dist/async.js:1019:9
at Object.eachLimit$1 (/home/kali/cloudsploit/node_modules/async/dist/async.js:3199:24)
at /home/kali/cloudsploit/collectors/aws/collector.js:109:23
at replenish (/home/kali/cloudsploit/node_modules/async/dist/async.js:1014:17)
at /home/kali/cloudsploit/node_modules/async/dist/async.js:1019:9
at Object.eachOfLimit (/home/kali/cloudsploit/node_modules/async/dist/async.js:1044:24)
at /home/kali/cloudsploit/collectors/aws/collector.js:88:19 {
code: 'TypeError',
time: 2024-09-04T21:18:03.251Z
}
Node.js v18.20.1
The text was updated successfully, but these errors were encountered: