-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
502 bad gateway when npm install #16
Comments
Sorry I made a dumb mistake, I forgot to include subfolder in the repo url:
Now it is working. |
Thanks for pointing this out, I'm glad that you make it work. But the link without subfolder should also work. As reported in the logs, the error is I searched about this error message, and I found this is because of the limitation of aws lambda (vercel now is on it), as talked in this issue. The invocation payload maximum limit is 6MB. Thus, if the repo is very large, the file size exceeds 6MB, then the request will fail. I don't know how to overcome this limitation, ideas are welcome~ |
Hi, thank you for this very useful project.
I was able to make it work perfectly, but now I have an error when running:
Which gives me:
I think that what causes the issue is that the repository
https://github.com/MrHertal/amplify-cli
is a fork that I deleted (for personal reason) then recreated again. Since I did that, it does not work anymore.Thank you for your help.
The text was updated successfully, but these errors were encountered: