Installing issue via npm with https://npm.greensock.com/@gsap%2fshockingly

[Jaywing Australia]

Hi, We use the private gasp npm registry, and it was working ok until today we notices that there are some issues with

https://npm.greensock.com/@gsap%2fshockingly

during 

npm install 

we get

 

npm ERR! code E504
npm ERR! 504 Gateway Time-out - GET https://npm.greensock.com/@gsap%2fshockingly/-/shockingly

Are you aware of any problems as this is failing deploys on our CI

 

Best Regards
Gin

[rubyplaynetwork]

We have also encountered this issue, but with @gsap%2fbusiness.

[phyllisstein]

I've been seeing the same issue. Attempts to install @gsap/shockingly from the private registry throw 504s on my local machine and in the cloud, with both NPM and Yarn.

 

HttpErrorGeneral: 504 Gateway Time-out - GET https://npm.greensock.com/@gsap%2fshockingly
    at /Users/daniel/.config/yarn/global/node_modules/pacote/node_modules/npm-registry-fetch/lib/check-response.js:95:15
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async RegistryFetcher.packument (/Users/daniel/.config/yarn/global/node_modules/pacote/lib/registry.js:87:19)
    at async viewMany (/Users/daniel/.config/yarn/global/node_modules/npm-check-updates/build/src/package-managers/npm.js:400:18)
    at async viewOne (/Users/daniel/.config/yarn/global/node_modules/npm-check-updates/build/src/package-managers/npm.js:448:20)
    at async distTag (/Users/daniel/.config/yarn/global/node_modules/npm-check-updates/build/src/package-managers/npm.js:586:24)
    at async getPackageVersionProtected (/Users/daniel/.config/yarn/global/node_modules/npm-check-updates/build/src/lib/queryVersions.js:70:29)
    at async /Users/daniel/.config/yarn/global/node_modules/p-map/index.js:57:22 {
  headers: [Object: null prototype] {
    server: [ 'nginx/1.14.0 (Ubuntu)' ],
    date: [ 'Mon, 24 Jun 2024 03:58:33 GMT' ],
    'content-type': [ 'text/html' ],
    'content-length': [ '192' ],
    connection: [ 'keep-alive' ],
    'x-fetch-attempts': [ '1' ]
  },
  statusCode: 504,
  code: 'E504',
  method: 'GET',
  uri: 'https://npm.greensock.com/@gsap%2fshockingly',
  body: <Buffer 3c 68 74 6d 6c 3e 0d 0a 3c 68 65 61 64 3e 3c 74 69 74 6c 65 3e 35 30 34 20 47 61 74 65 77 61 79 20 54 69 6d 65 2d 6f 75 74 3c 2f 74 69 74 6c 65 3e 3c ... 142 more bytes>,
  pkgid: '@gsap/shockingly@*'
}

 

It's a particular nuisance for my Docker environments, as they don't have long-lived caches and have begun to fail on routine teardown/rebuild operations during development.

Edited June 24 by phyllisstein
Add note about Docker.

[smit.bhikadiya]

Facing same issue

npm ERR! 504 Gateway Time-out - GET https://npm.greensock.com/@gsap%2fshockingly/-/shockingly-3.7.1.tgz

[JefCurtis]

Same issue here:

265.4 npm ERR! 504 Gateway Time-out - GET https://npm.greensock.com/@gsap%2fshockingly/-/shockingly-3.12.5.tgz

[Carlos Lorca]

Same issue: ERR! 504 Gateway Time-out - GET https://npm.greensock.com/@gsap%252fbusiness

[sooyoos]

Same issue here 
 

yarn install v1.22.22 [1/4] Resolving packages... [2/4] Fetching packages... info There appears to be trouble with your network connection. Retrying... info There appears to be trouble with your network connection. Retrying... info There appears to be trouble with your network connection. Retrying... info There appears to be trouble with your network connection. Retrying... error Error: https://npm.greensock.com/@gsap%2fshockingly/-/shockingly-3.12.2.tgz: ESOCKETTIMEDOUT at ClientRequest.<anonymous> (/home/deploy/.nvm/versions/node/v18.20.3/lib/node_modules/yarn/lib/cli.js:142037:19) at Object.onceWrapper (node:events:631:28) at ClientRequest.emit (node:events:517:28) at TLSSocket.emitRequestTimeout (node:_http_client:847:9) at Object.onceWrapper (node:events:631:28) at TLSSocket.emit (node:events:529:35) at Socket._onTimeout (node:net:598:8) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

 

[rawker]

I have the same issue. 
It's been going on since yesterday.

[Dinamo]

same issue here from yesterday
 

npm ERR! 504 Gateway Time-out - GET https://npm.greensock.com/@gsap%2fshockingly/-/shockingly-3.12.5.tgz

 

[Remco]

Same here.. 504 Gateway Time-out on both @gsap/business but also the free version :(. 

 

[Cassie]

Hi folks!

 

So sorry about this - I've contacted @Prasanna from PrivJS who handle the private repo and asked them to look into it as a matter of urgency.

I'll keep this thread updated. 

 

If you have the option of switching out install methods, you can use the .tgz file for now. That's not reliant on the private repo, just drop the zip file into the root of your project and npm install it.

https://gsap.com/docs/v3/Installation/?tab=npm&module=esm&method=zip&tier=free&club=true&require=false&trial=true
 

npm install ./gsap-bonus.tgz

[TAKTIK]

Same here:

#12 532.7 npm ERR! code E504

#12 532.7 npm ERR! 504 Gateway Time-out - GET https://npm.greensock.com/@gsap%2fbusiness

[pixelart]

@Cassie This has happened quite often over the last few years. This is really critical when I cannot deploy something on a production site. Any chance you are looking into this to be fixed for good?

It would be a shame if I would have to work with the tgz-files as the update-process is pretty annoying.

 

I love working with gsap and this is really the only negative aspect I encounter from time to time 💔

[Cassie]

Entirely understood, it's incredibly inconvenient and not good enough for a paid service.

The last two times this issue occured it was due to Digital Ocean’s network going down (which is what PrivJS leverages) This took our private repo down with it. PrivJS since migrated away from Digital Ocean in order to avoid this happening again. 

I'm afraid I can't comment on what the issue is currently, but we're also at the limits of our patience with this. Unfortunately the .tgz route is the only  solution I can recommend right now as it's not reliant on any third party services, so although it is annoying to update, it is bulletproof.

 

We will do a retro after this and see if this is something we can handle differently. 
 

[Codex Digital]

I'm just relieved it's not on my end, thanks for the updates Cassie. 

[derekobrien]

Thanks for the update,

Appreciate a swift resolution to this as its holding up deployments our side :)
 

npm ERR! code E504
npm ERR! 504 Gateway Time-out - GET https://npm.greensock.com/@gsap%2fshockingly

[Cassie]

@Remco - Just clarifying that this won't be affecting the normal GSAP repo as it's housed elsewhere - I've just attempted an install and it works a ok.

If you're struggling it's likely due to an old package.lock file referencing the private repo. Make sure to delete node modules and the package.lock and try a fresh install.

 

Let me know if you need assistance with this and I'll pop you a DM

[pixelart]

@Cassie thx, really appreciate your work

[Cassie]

I appreciate your kindness and patience during this @pixelart !

[Cassie]

Hi everyone,

 

Looks like we're back online again. ✨ 

 

Again, so sorry for this disruption.

[Rayan Boutaleb]

Hello @Cassie,
We hit the same error at the same time OP did, and I followed this thread closely.
It seems to be fixed, but we're still hitting the same error code when deploying on cloudflare (vercel seems to work) with the `gsap/react` import.
We cleared cloudflare cache etc, but the build is still failing.
Could this be linked to the original issue, as the build used to work well prior yesterday's issue, and now fails ( but works on vercel ? )

Thanks a lot,

[Cassie]

Just to clarify - still a 504 error? 

 

[Rayan Boutaleb]

Yes, this is my error :
( only difference I can see is that we are on business-3.12.5.tgz ? )

npm ERR! code E504
npm ERR! 504 Gateway Time-out - GET https://npm.greensock.com/@gsap%business/-/business-3.12.5.tgz

[Cassie]

Have you tried deleting your package lock and node modules and starting over? Sorry if that's not how cloudflare deploys work. I'm a little out of my depth now I'm afraid.

The 504 error should only be around if the private repo isn't up and it's definitely up now. I would guess there's some sort of caching issue? 

[Sunnypsm]

Hi @Cassie

Thanks for keeping the community updated, I can confirm its all back to normal now,