Jump to content
GreenSock

Prasanna

Members
  • Posts

    34
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Prasanna's Achievements

  1. Hi, In windows you can set the env variables in a pretty straightforward manner - using the Environment variables dialog. Reference: https://docs.oracle.com/en/database/oracle/machine-learning/oml4r/1.5.1/oread/creating-and-modifying-environment-variables-on-windows.html#GUID-DD6F9982-60D5-48F6-8270-A27EC53807D0 On a macbook, you can run the following command to set the env variable: $ echo "export NPM_GREENSOCK_TOKEN=xxxx-xxxx" | sudo tee -a ~/.zshrc Let me know if this helps Prasanna
  2. @Rodrigo It seems like the greensock registry was not set for the computer. How about we debug this over google meet?
  3. @Rodrigo thanks for reporting. It seems like you might have missed configuring the scoped registry on the machine. This can be resolved by running these commands: $ npm config set @gsap:registry https://npm.greensock.com/ $ npm config set //npm.greensock.com/:_authToken xxxx-xxxx-xxxx-xxxx $ yarn add @gsap/shockingly gsap@npm:@gsap/shockingly Running the above commands should help. If you still face issues then I can help you by providing a sample yarn configuration file (for yarn berry). Here are some additional resources that could be helpful: https://blog.privjs.com/article/how-to-install-club-greensock-packages-on-digitalocean-aws-etc https://blog.privjs.com/article/how-to-install-club-greensock-packages-on-netlify
  4. The registry service used by npm.greensock.com uses the official npm registry as fallback registry. Hence you would still be able to install all packages when you set npm.greensock.com as the global registry. There is no problem with configuring npm.greensock.com as the global registry but package installation could be slower in some cases (in cases when the package requested is not readily available in the npm.greensock.com registry) As for the fallback registry, it is currently not possible to set two global registries. But you can set a registry for scoped packages and use global registry as a fallback.
  5. Yes it does, but as a practice it is recommended no to commit tokens/keys in your project.
  6. Hi @Cassie, thanks. I created this repo for installing via yarn: https://github.com/prasannamestha/gsap-netlify-yarn Only difference between using npm and yarn is that yarn needs an explicit install for `@gsap/shockingly` Let me know how it goes for you Prasanna
  7. Oops, my bad. I just made the repo public.
  8. Hi @Cassie Here's an example repo with instructions in it: https://github.com/prasannamestha/gsap-netlify Netlify deployment URL: https://modest-bose-c7e4b6.netlify.app/ I hope this helps
  9. Hi @Cassie, We have a tutorial with sample github repo on deploying greensock package to netlify. I will post the link to it here tonight.
  10. @Puneet Sharma Can you run the following steps and let us know if you're still facing issues: $ npm config set registry https://npm.greensock.com $ npm config set @gsap:registry https://npm.greensock.com $ npm config set //npm.greensock.com/:_authToken <your-token-here> $ yarn add @gsap/shockingly
  11. Hi @Puneet, did you try either one of the methods mentioned in this comment:
  12. I just received an update from DeployHq: In order to use a private npm package within the build pipeline, you'd need to create an auth.json file, including the password/token to access the private repo. You can set this up as a config file within DeployHQ, to stop you from having to save sensitive data within your repository: https://www.deployhq.com/support/config-files This should solve the problem @Stoggy
  13. @Stoggy - can you help us with the package.json file? (Only the line containing `@gsap/shockingly` dependency would be sufficient) Update: You need to set the config in DeployHQ:
  14. Hey all, apologies for the delay in my response - I was out travelling last week. The problem with yarn classic is that `$yarn install` might not work with package name aliases. So this means: * $yarn add gsap@npm:@gsap/shockingly -> this works * import GSAP from 'gsap' -> this works But, if you run $ rm -rf node_modules and then run $ yarn install - the installation fails. This is because yarn classic has an active bug with package name aliases which defaults to the default npm registry. So, as a workaround you can do either of these: 1. Do not use package name alias: $ yarn add @gsap/shockingly -> and then import GSAP from '@gsap/shockingly' 2. Set the global registry to Greensock: $npm config set registry https://npm.greensock.com and follow the rest of the instructions specified: https://greensock.com/docs/v3/Installation#private
×