-
Notifications
You must be signed in to change notification settings - Fork 491
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
Cannot find module when running test on Fargate #2751
Comments
Very odd, looks like the dependencies are not being discovered as expected. Will try to repro here! |
Did some tests again this morning and I believe this has to do with the fact that the yamls are stored in subfolders. If I move the yml and js file to the root, I can see all files being bundled.
And everything goes as expected. Note I had another issue when installing packages (error 401) because my |
@madhugod 👋 Glad you got it working. Could you let me know what was your original folder structure like (and where you were running the test from, relative to that)? I'm interested in trying to reproduce your original issue.
We have to document this better, but yes there is a way. It depends what private registry you're using, but it's possible to set some variables that Artillery will pick up to use a private registry. If you end up needing this, let us know! |
Hello @bernardobridge My original folder structure looks like this (minus node_modules folder):
I was running artillery commands at the root, example:
|
Thanks @madhugod 🙇 ! Can't reproduce it on Mac, so it could be windows-specific. Will try it out on a windows machine when I have a chance. |
Version info:
Running this command:
I expected to see this happen:
I expect the test to be ran successfully.
Instead, this happened:
But the console says:
And in the CloudWatch logs I can see the following error:
Files being used:
Note that
bcrypt
package is installed (in both package.json, package-lock.json and node_modules)It is also used (via require keyword) in the function.js file that is referenced in the
processor
field of the login.yml fileThe text was updated successfully, but these errors were encountered: