Meet Bhatt
Content Type
Profiles
Forums
Store
Blog
Product
Showcase
FAQ
Downloads
Posts posted by Meet Bhatt
-
-
3 minutes ago, Prasanna said:
Hello @Meet Bhatt, yarn tries to install all packages when you run the install command. That's likely the reason why .tgz install failed.
Regarding the vercel issue, can you try to follow the steps mentioned in this article and see if that helps? https://blog.privjs.com/article/how-to-install-club-greensock-packages-on-vercel
I tried an npm install too just to check, same thing - it was still trying to reach the registry. Though that's not an issue anymore.
-
5 minutes ago, Prasanna said:
Hello @Meet Bhatt, yarn tries to install all packages when you run the install command. That's likely the reason why .tgz install failed.
Regarding the vercel issue, can you try to follow the steps mentioned in this article and see if that helps? https://blog.privjs.com/article/how-to-install-club-greensock-packages-on-vercel
Thanks for the quick turnaround @Prasanna. So I have been deploying on vercel for months now. Only since earlier today have I been getting errors. First it was a 502. After your notification of it being fixed, its a 403 now
I tried generating a new token from the dashboard just to check if that was the problem. That didn't work too -
48 minutes ago, GreenSock said:
I'm confused about how a local file could "time out". Perhaps I'm missing something obvious (?)
I think the npm install on the .tgz still tries to download something from the registry, and that request times out.
Also still getting a 403 on vercel. Works fine locally now. -
1 minute ago, Meet Bhatt said:
Facing the same issue at the moment (502 Bad Gateway) while trying to install my shockingly green module. The "npm-install-this" version is timing out locally too.
Any ETA on this folks?
-
Facing the same issue at the moment (502 Bad Gateway) while trying to install my shockingly green module. The "npm-install-this" version is timing out locally too.
Business https://npm.greensock.com/ registry is down
in GSAP
Posted
Okay sorry this was a problem on my end. The lockfile had been messed up while I was frantically trying to install the package. That was causing the errors on vercel.
Thanks folks!