Prasanna

Hello @Basebuilder, it appears that the version of yarn cli that you are using in bitbucket pipelines could be the issue. Can you try doing this instead: Run this command once in the repo $ yarn add @gsap/business gsap@npm:@gsap/business This should fix the pipelines.

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

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 👍

Hello @thefa, Adding a .npmrc file to your project should solve the problem. Steps: 1. Add a new file `.npmrc` in your project root 2. Add the following content in the `.npmrc` file: ``` @gsap:registry=https://npm.greensock.com //npm.greensock.com/:_authToken=xxxx-yyyy-zzzz ``` 3. Replace `xxxx-yyyy-zzzz` with your access token Pro tip: You can also store the token as env variables

Hello @derekobrien, I don't have an auth.json file with me, but I believe now you can use environment variables instead as well. (https://www.deployhq.com/support/config-files#environment-variables). You only need to add a .npmrc file to your project: @gsap:registry=https://npm.greensock.com //npm.greensock.com/:_authToken=${PRIVJS_TOKEN} Then add an environment variabled named `PRIVJS_TOKEN` in your deployHQ server. This should install the packages from greensock registry.

Hello everybody, I am sorry that you faced an issue. Our services went offline intermittently today as we experienced a DDOS attack on our systems. There's nothing to worry as our service actively fended off the attacks, but couldn't serve few users for a short while. We have increased our server capacity in order to prevent such scenarios in the future. My apologies for the inconvenience

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

Hello everybody, my sincere apologies for all these issues. In the last 24 hours we recieved a massive number of requests which our cloud service failed to handle. The services are back online now. Our team has also put measures to prevent this from happening again. Going forward, we will be migrating our services to multiple cloud services in order to prevent any downtime. I am very sorry for the troubles you faced in the past 24 hours. Prasanna

Hello everybody, my sincere apologies for all these issues. In the last 24 hours we recieved a massive number of requests which our cloud service failed to handle. The services are back online now. Our team has also put measures to prevent this from happening again. Going forward, we will be migrating our services to multiple cloud services in order to prevent any downtime. I am very sorry for the troubles you faced in the past 24 hours. Prasanna

I tried replicating it with yarn version 1.0. It is strange that yarn is not reading the env variables. Since you are using yarn, it could help if you rename `.npmrc` to `.yarnrc`. If this still doesn't help, then running the commands on the machine should configure the values: ``` $ yarn config set @gsap:registry https://npm.greensock.com $ yarn config set //npm.greensock.com/:_authToken <token here> ```

Hello @Sgt. Red Pepper, 403 error is returned when the yarn or npm cli doesn't get the GSAP token value. Usually yarn cli reads the .npmrc file in the project, but some versions require a .yarnrc file. It would be helpful to know which version of yarn you are using. Also, can you make sure whether the env variable is added to the container/vpc? Please note that the variable needs to be exposed to the machine where the `yarn install` command is run. (Many projects don't expose env variables to docker instances hence 403 errors) Let me know if this helps

@stectix - I was able to get the typescript app running without issues. Maybe this line is not needed in your typescript config? "files": ["./node_modules/@gsap/business/types/index.d.ts"], I created a github repo for reference: https://github.com/privjs/gsap-typescript-example

@stectix It seems like gsap package has been installed. Now, the typescript issue here is project-specific as there are various configurations involved. I'd recommend setting esModuleInterop as true, and maybe check the `node_modules` directory and test whether the type file exists?

@stectixsorry about the late response, just saw the message. The error is weird - could be due to older version of yarn. If possible, please update the yarn version or use npm to install the package - it should fix it. If the above suggestion is not an option, I'd recommend doing this: 1. Run: `$yarn add @gsap/business` 2. import like this: `import gsap from '@gsap/business'` 3. import types like this: ``` "files": [ "node_modules/@gsap/business/types/index.d.ts" ] ``` Let me know if this helps. Otherwise I'd be happy to hop on a google meet call as well.

Hi @stectix, @Rodrigo This seems to be a confusion caused by npm package aliasing. If you install the package using this command: `yarn add gsap@npm:@gsap/business` then the import should be `import gsap from 'gsap'`. This should work as the package manager creates a folder named `gsap` in the `node_modules` directory. If you did this, then add the following to compiler options: ``` "files": [ "node_modules/gsap/types/index.d.ts" ] ``` Let me know if this works