Not seeing the "club" plugins on a business account

[cmm]

I am not seeing the "club" plugins in the node_modules/gsap directory after adding token stuff to .npmrc and doing the gsap@npm:@gsap/member.  I have a business account.  No errors on npm commands.

[Cassie]

Hey there,

What does your package.json look like currently?

[cmm]

 and node_module

 

[Rodrigo]

Hi,

 

It should actually look like this:
 

"dependencies": {
  "gsap": "npm:@gsap/business@^3.12.5",
   ...
}

You're not getting any errors when installing the GSAP bonus package? This

"npm:@gsap/member@^3.12.5"

With member in it is very odd, actually there is no package in our repo with that as far as I can tell. You should run this:

npm install gsap@npm:@gsap/business

Try removing that gsap dependency, delete your package-lock.json file, create an .npmrc file and then try to install using the instructions here:

https://gsap.com/docs/v3/Installation

 

Hopefully this helps.

Happy Tweening!

[cmm]

So I removed the entry in package.json,  removed package-lock.json,  removed the gsap dir from node_module, replaced the contents of .npmrc with:

always-auth=true
//npm.greensock.com/:_authToken=(my token number here)
@gsap:registry=https://npm.greensock.com

 

and ran ...

npm install gsap@npm:@gsap/business

 

and get this error:

npm ERR! code E403
npm ERR! 403 403 Forbidden - GET https://npm.greensock.com/@gsap%2fbusiness - you don't have access to this package: @gsap/business
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.

 

 

also the "

"npm:@gsap/member@^3.12.5"

entry that was in my package.json came from running   npm install gsap@npm:@gsap/member   as was instructed on the installation page. 

 

Could you check My Account and confirm that the business license is still in tack?

 

Thanks for the quick response.         

[Cassie]

Hi again, Just a note to say we're looking into it as a matter of urgency.

'member' should have been 'business' on the install page. Apologies for leading you down a bad path here.

We'll pop back as soon as we know more

[Cassie]

Hi there! 

 

We've pressed some knobs and switched things off and on again and you should be all set now.

 

We generated a new token for you. If you go to the install page, and hard refresh you should see the new token and the correct 'business' tier instructions

I think this little blip happened because your business membership was from quite a while ago - 2014! Something must have gone a bit wonky during those years.

 

Thanks for all the support and sorry for the trouble.

[cmm]

Thanks Cassie,

 

It's working as expected.

[Cassie]

Wonderful! Thanks for your patience.