Unable to deploy my Next.js app with Greensock Business included.

[artvera]

Hello, I am unable to deploy my Nextjs app with Vercel. I keep getting the error that I attached in the email. I tried following the instructions provided by Greensock, but to no avail. Has anyone encountered this problem before? Thank you in advance.

[GreenSock]

Sorry to hear about the trouble, @artvera. Have you tried the steps mentioned here?: 

Or here?

 

[artvera]

@GreenSock Nothing works, I still have the same error. I don't understand why it's so complex. I'm going to try with Locomotive Scroll or Framer Motion, I don't have time to dwell on this problem, I have to deploy this site quickly.

 

Thank you anyway

[GreenSock]

Very sorry, @artvera. I'm not at all familiar with Vercel or Next.js but I know for sure that GSAP works with them. Gosh I wish I had a silver bullet to offer. I'll ping @Prasanna who is our resident expert on all things with private repos. So none of the information in those threads helped? It seemed like folks got it working by the end of the thread and offered advice. Did you make sure you used your token? 

[artvera]

Thank you very much, I just found an interesting solution that works using the .tgz folder while waiting for a better solution. In case it can help someone:

 

[Rodrigo]

Hi @artvera,

 

Sorry about the issues. After a few trial and error deployments I managed to successfully deploy a NextJS app into Vercel using the Shockingly package (you are a business member, but the files in both packages are the same).

 

Here is how the .npmrc file looks like:

always-auth=true
@gsap:registry=https://npm.greensock.com
//npm.greensock.com/:_authToken=${NPM_TOKEN}

Here is the repo just in case:

https://github.com/rhernandog/gsap-bonus-npm-vercel

 

And here is the live site, the console is logging the MorphSVG plugin Object:

https://gsap-bonus-npm-vercel.vercel.app/

 

Hopefully this  helps.

Happy Tweening!

[artvera]

@Rodrigo @GreenSock Thank you very much for your responsiveness, my website is now online and everything is working perfectly. @Rodrigo Your solution works perfectly well.