Deployment issue with DeployHQ - GSAP shockingly bonus plugins E403 Forbidden

[Stoggy]

Hi, 

 

I'm trying to deploy using DeployHQ but it fails during the npm install phase due to auth errors.

 

npm ERR! code E403
npm ERR! 403 403 Forbidden - GET https://npm.greensock.com/@gsap%2fshockingly/-/shockingly-3.8.0.tgz - You must be logged in to install/publish packages.
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.

 

It works great locally with no problems at all.

 

I've added the .npmrc file with these lines in it:  (AUTH_TOKEN being replaced with my token)

//npm.greensock.com/:_authToken=${AUTH_TOKEN}

@gsap:registry=https://npm.greensock.com

 

Any suggestions on how to solve this?

[Cassie]

I don't really know much about deployHQ - have you tried reaching out to them for support?

 

https://www.deployhq.com/support/build-errors/dependency-not-found <- maybe there's something in their docs to help?

[Stoggy]

8 minutes ago, Cassie said:

I don't really know much about deployHQ - have you tried reaching out to them for support?

 

https://www.deployhq.com/support/build-errors/dependency-not-found <- maybe there's something in their docs to help?

Well it seems to me that this is an authentication problem and not that the dependency is not found. 

I have not, but i'll check with them as well! 

[Cassie]

Maybe @Prasanna has some pointers?

[GreenSock]

I wonder if either of these threads might help, @Stoggy:

 

 

https://greensock.com/forums/topic/28152-netlify-deploy-error-with-greensock-member/page/2/?tab=comments#comment-139248

?‍♂️

[Prasanna]

@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: 

 

 

 

[Prasanna]

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

[Stoggy]

Thanks @Prasanna I'm sure it will work since they gave me the same answer!

 

Will have to try in my next project. This time i solved it by adding gsap as a zip.

[derekobrien]

Anyone have an example auth.json file that DeployHQ accepts for GSAP shockingly? Getting same issue but can't see how to convert .npmrc to auth.json

 

[Prasanna]

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.

[derekobrien]

Thanks Prasanna,

 

Will give that a try ?