What happens with other projects when we generate a new token?

[MOQO]

Hi.

 

I am wondering what will happen if we accidentally generate a new token to use our GSAP Business.

What happens to our existing projects? Will this harm any existing projects that uses the old token?

 

Or will code that has been build stay intact with that new token?

[mvaneijgen]

Everything will stay intact. The token is just to get the bonus plugins from the private NPM repo, the only thing that changes is that when you `npm install` the old project again and the package aren't cashed from last time (or there is an update) the install will fail, but than just changing the token in your `.npmrc` file will fix the issue. 

 

None of the GSAP plugins have "phone home" scripts that report usage or suddenly cause things to stop working if your license expires or when you update your token. We extend respect to our users and trust that it'll be reciprocated. 

 

Hope it helps and happy tweening! 

[GreenSock]

Yep, @mvaneijgen is exactly correct. The token is only used for accessing the private repository. And by the way, you can download the zip file from your account dashboard or the install page and use the "gsap-bonus.tgz" file instead of the private repository. You can literally "npm install ./gsap-bonus.tgz" and it's just like it pulled it in from the repository, but it's using that local file instead. Obviously in the future then if you want to update the files, you'd have to do that same process again (so if you're updating a lot, the private repository might be a little bit easier). I'm just trying to explain that you don't NEED to rely on the private repository (and token) if you don't want to. 

 

Thanks for being a Club GSAP member! 💚