-
Notifications
You must be signed in to change notification settings - Fork 22
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 require()
package
#39
Comments
All that would be needed is just update the |
I have same issue as well (version 2 is working, but not version 3), seeing same runtime error. |
I have the same issue. I have to move to v3.0.0.0 and now getting the same error. How did you resolve it? |
Hi @IgnacioPinedo @HenryLuoOne @cherath, have you found any solution of this issue ? |
Just as a note, we still have not resolved this. Currently I have all my functions using AWS v3 expect credstash which is still using v2 due to this issue. |
Just waiting until it's released and I'll close the issue. The action to release is failing due to a token issue. |
Hi All,
Thanks for letting us know.
Kind Regards,
Chulani
…________________________________
From: Ignacio Pinedo ***@***.***>
Sent: Tuesday, 17 October 2023 8:02 AM
To: DavidTanner/nodecredstash ***@***.***>
Cc: cherath ***@***.***>; Mention ***@***.***>
Subject: Re: [DavidTanner/nodecredstash] Cannot `require()` package (Issue #39)
Closed #39<#39> as completed.
—
Reply to this email directly, view it on GitHub<#39 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AETMWGK4SDSETZ3FN2A4JLTX7WOFPAVCNFSM6AAAAAAS64EGTGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQGY3TANRTG4ZDENI>.
You are receiving this because you were mentioned.
T
|
I've used
nodecredstash@2.0.2
for a while now, but wanted to upgrade to leverage theaws-sdk
v3 separate modules and decreasednode_modules
folder size. Unfortunately the repo I use it in doesn't support ES6 and I can'trequire()
the package. This is the error I'm seeing:It would be nice if the package was imported using CommonJS instead of ES6, that way it could be used in both ES6 and non-ES6 repos.
To reproduce you only need to try and
require()
the package in any file. An easy way to do this, is by going to the npm package RunKit and clicking run.The text was updated successfully, but these errors were encountered: