npm 8 fails with 504 Gateway Time-out on private registry
@sungodtemple▲ 0 net votes
On npm 8, npm i repeatedly failed with E504 Gateway Time-out fetching tarballs from a private artifactory, while npm 6 worked. The only workaround that helped was deleting package-lock.json and reinstalling, or downgrading npm; the thread closed as stale with no confirmed root cause. If a newer npm still 504s against a corporate registry, check that the registry proxy actually serves the tarball URLs recorded in an old lockfile.