Request for Assistance with GSAP Business License Installation Issue

[4eck-media]

Dear GSAP Support Team,
 

I am writing on behalf of the 4eck-media development team. We are currently utilizing the GSAP Business license for our project and have recently migrated our website from a development VPS server to a live VPS server. As part of this process, we are installing all necessary npm dependencies as per the instructions provided.
 

We have correctly added the requisite lines to our .npmrc file, both at the profile level and at the root of our project:

//npm.greensock.com/:_authToken=********-***
@gsap:registry=https://npm.greensock.com

We have also attempted to install GSAP to our project using the command npm install gsap@npm:@gsap/business. However, we are encountering issues during the installation process.

When using npm, the installation process stalls at the stage (⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠙ idealTree:frontend: sill idealTree buildDeps.

When using yarn, the process consistently ends with the error message info There appears to be trouble with your network connection. Retrying...

 

We have confirmed that the issue is specific to the gsap/business package, as all other packages install without issue. We have attempted various troubleshooting methods, but have yet to find a solution. We would greatly appreciate your assistance in resolving this issue.

 

We initially attempted to reach out via your contact form, but encountered a 500 error.

 

Best Regards,
Slava Weber
Team Lead, Development Team
4eck-media

[Cassie]

Hi there, sorry for the frustration. Private repos can be a bit tricky sometimes.

Paging @Prasanna - he's our priv.js expert!

In the interim could you maybe try this?

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

 

[Prasanna]

Hello @4eck-media, could you check if your live servers have any domain whitelist? In some servers devops engineers enforce domain name whitelisting in order to prevent unintended requests. If your servers have the same, kindly add `https://npm.greensock.com` to the whitelist and everything should work fine 👍

[4eck-media]

I apologize for the delayed response. Our issue was related to the security system (firewall) settings on our server; coincidentally, the server was blocking some requests. After adjusting the security configurations, we resolved the problem.
 

I am grateful for your response and this code(always-auth):

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

It would be great to have this code in the documentation.

[Cassie]

@Prasanna - would you be able to give me a little TLDR breakdown of what the always-auth line does and when it's useful? It seems like it's helped a few people so maybe we should add it as a note on the install page?

[Prasanna]

Hello @Cassie, `always-auth=true` forces npm to always require authentication when accessing the registry.  However, this is an optional command and is only required in some scenarios, but feel free to add it
You cal also link it to a tutorial on PrivJs Blog if that's helpful to the users: https://www.privjs.com/blog/how-to-install-club-greensock-packages-on-vps

[Cassie]

I'll get that tutorial added too. Thanks Prasanna!