-
Notifications
You must be signed in to change notification settings - Fork 307
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
Webpack failure TypeError: hexoid is not a function #798
Comments
Hi @maryamaljanabi - thanks for raising this What version of |
@adamjmcgrath Thanks for your response. I'm not using
|
Hi @maryamaljanabi - could you share a repo that demonstrates the issue? I'm not able to reproduce it with the steps you've shared |
Hi @adamjmcgrath thanks a lot for responding again. I could reproduce this issue on both Windows and Ubuntu. I'd appreciate any feedback on how to solve this. I get the error when running |
I also am having this problem. We are using 3.2.0 and run into the exact same problem on AWS Lambda, after disabling superagent-proxy like the Readme says. |
I figured out a workaround @maryamaljanabi: #657 (comment) specifically what NotMyself commented on Sep 27, 2021. |
Thank you for mentioning that @bxjw. Since I'm using |
For anyone struggling with this issue while using
Another solution is to downgrade
I ended up going with the first solution and just disabling Update: Disabling
|
Why has this issue been closed? This library clearly does not work properly in a node environemnt in a aws Lambda. |
I encountered issues:
finally #828 works fine for me(sls v1.67, Nodejs14), and watch out the Reference: AnomalyInnovations/serverless-nodejs-starter@master...adamjmcgrath:serverless-nodejs-starter:master |
thanks for this a link i fixed this ERORR: [!hexoid is not a function] |
i encountered the same issue when I used the formidable |
Describe the problem
When running my nodejs serverless application that uses anything from
auth0
, I get the following error:What was the expected behavior?
The application should not throw an error and accessing the features of
auth0
package should be accessed without a problem.Reproduction
yarn add auth0 @types/auth0
yarn start
auth0
Environment
It's worth mentioning these versions that I'm using:
@types/auth0
: 3.3.0serverless
: 2.66.0serverless-bundle
: 5.0.2serverless-offline
: 8.2.0aws-sdk
: 2.684.0nodejs
tried all these versions but the error didn't go away (14.19.0, 16.17.0, 18.12.0)The text was updated successfully, but these errors were encountered: