What you see
npm ERR! code E429
npm ERR! 429 Too Many Requests - GET https://registry.npmjs.org/@babel%2fcoreCommon causes
- Many runners sharing one public IP address through NAT, so the registry sees them as one very busy client.
- Matrix builds that install the same dependencies in dozens of jobs at once.
- Scripts that call npm view or npm outdated in loops.
How to fix it
- 01
Spread the load
Reduce parallel installs, or install once and share node_modules between jobs as an artifact.
shell npm ci --prefer-offline - 02
Use one cache for every runner
A registry cache turns hundreds of runners into one well-behaved client upstream.
.npmrc registry=https://acme.cacheport.cc/npm/ //acme.cacheport.cc/npm/:_authToken=${CACHEPORT_TOKEN}