Have an issue in deployment build (errno ETIMEDOUT)

[Clear Digital]

Already have image (with digest): us-docker.pkg.dev/prod-decoupled-shared/build-tools/pantheon-build:v1.1.0-node20
The framework expected according to the configuration is: next.
The framework detected from the code is: next
npm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm WARN deprecated domexception@4.0.0: Use your platform's native DOMException instead
npm WARN deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm WARN deprecated wrench@1.3.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
npm WARN deprecated glob@7.1.7: Glob versions prior to v9 are no longer supported
npm WARN deprecated node-domexception@1.0.0: Use your platform's native DOMException instead
npm WARN deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code ETIMEDOUT
npm ERR! syscall connect
npm ERR! errno ETIMEDOUT
npm ERR! network request to https://npm.greensock.com/@gsap%2freact/-/react-2.1.2.tgz failed, reason: connect ETIMEDOUT 104.131.8.206:443
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in: /builder/home/.npm/_logs/2026-01-06T12_35_06_209Z-debug-0.log

Hi, I'm recently experiencing an error in my deployment build, and I can't figure out what the issue is. Can anyone let me know the problem and help me to fix this?

[GreenSock]

Ah, it looks like at some point you were using the "members-only" Club GSAP files which previously required special access to a private repository (evidenced by the "npm.greensock.com" reference in your error message). It almost surely involved a .npmrc file that told your system to find that "gsap" package at npm.greensock.com, but that .npmrc file is no longer necessary because Webflow made GSAP free for everyone back in April 2025! No more "members-only" access. No more Club GSAP. It's now super easy for anyone to access all the files (including the bonus ones) without any special tricks, custom URLs or .npmrc files. Here are the migration instructions: 

https://gsap.com/resources/private-repo-migration/

 

It's just a matter of using the typical public repository. Or snag the files from Github or download them from our site. Whatever works best for your workflow. https://gsap.com/install

 

My guess is that you've got an .npmrc file lurking on your system (it could be further up the directory tree) that's interfering and telling your build process to look for the "gsap" or "@gsap/react" package at npm.greensock.com instead of the standard public repository at npmjs.com. Once you remove that .npmrc file and update to the latest gsap version, I bet it'll work great. 

 

Enjoy! 💚

[Clear Digital]

Thanks! I removed the authentication token and reinstalled node modules, and it worked. 😃