Moving off the private repo
Thanks to Webflow's support, The core GSAP library and all the plugins are now 100% free for everyone! This page covers how to move away from the private repository.
If you're one of our wonderful Club GSAP members - you may be wondering what you need to change in your project to continue using the GSAP files you know and love.
The good news is that it's nice and simple from now on! No more tokenised access to a private repository, no more .npmrc files or fiddly yarn install issues. 🥳
NPM / Yarn (or other package managers)​
All the GSAP files are now publicly available on npm for everyone to use - just install GSAP with your package manager of choice.
- npm
- Yarn Classic
- Yarn Berry
Remove the following from your .npmrc -
.npmrcalways-auth=true
//npm.greensock.com/:_authToken=24e2f3ca-63e0-4b93-b68e-a4695672c571
@gsap:registry=https://npm.greensock.comRemove the Club GSAP dependency.
Take a look in your package.json to check which tier of Club GSAP you have installed.
package.json{
"name": "gsap-bonus",
"version": "0.1.0",
"private": true,
"dependencies": {
"@gsap/business": "^3.13.0",
"next": "14.2.3",
"react": "^18",
"react-dom": "^18"
}
}In this case we have the business package installed so we'll run the following in terminal.
bashnpm uninstall @gsap/business
Install the public gsap package
Now just install GSAP from the public repository, and you're done!
bashnpm install gsap
Remove the following from your .npmrc -
.npmrcalways-auth=true
//npm.greensock.com/:_authToken=24e2f3ca-63e0-4b93-b68e-a4695672c571
@gsap:registry=https://npm.greensock.com/Remove the Club GSAP dependency.
Take a look in your package.json to check which tier of Club GSAP you have installed.
package.json{
"name": "gsap-bonus",
"version": "0.1.0",
"private": true,
"dependencies": {
"@gsap/business": "^3.13.0",
"next": "14.2.3",
"react": "^18",
"react-dom": "^18"
}
}In this case we have the business package installed so we'll run the following in terminal.
bashyarn remove @gsap/business
Install the public gsap package
Now just install GSAP from the public repository, and you're done!
bashyarn add gsap
Remove the following from your .yarnrc.yml -
.yarnrc.ymlunsafeHttpWhitelist:
- "npm.greensock.com"
npmScopes:
gsap:
npmRegistryServer: "https://npm.greensock.com"
npmAuthToken: 24e2f3ca-63e0-4b93-b68e-a4695672c571Remove the Club GSAP dependency.
Take a look in your package.json to check which tier of Club GSAP you have installed.
package.json{
"name": "gsap-bonus",
"version": "0.1.0",
"private": true,
"dependencies": {
"@gsap/business": "^3.13.0",
"next": "14.2.3",
"react": "^18",
"react-dom": "^18"
}
}In this case we have the business package installed so we'll run the following in terminal.
bashyarn remove @gsap/business
Install the public gsap package
Now just install GSAP from the public repository, and you're done!
bashyarn add gsap
If you run into issues, you may need to delete node_modules
or lockfiles to ensure that nothing is referencing the old Club files.
# npm
rm -rf node_modules package-lock.json && npm install
# yarn classic
rm -rf node_modules yarn.lock && yarn install
# yarn berry (with PnP)
yarn install --immutable
For Yarn Berry: you may want to also check .yarn/cache and .yarn/unplugged folders if you had the Club package linked or cached.
Script Tags​
If you're using script tags in your project, there's nothing you need to change. Your self-hosted Club Plugins will continue to work! But if you would like the performance benefits of using a CDN, visit the install helper to grab your new links.