We have hit this issue multiple times in the past. While there is a few reports of the same kind of delay, there isn't much technical explanation available.
Your replications might be a few seconds or minutes behind the official database of record.
The delay is likely that the time taken for each CDN node to replicate the CouchDB metadata containing the package list, and it can take up to minutes. Therefore this PR goes conservative and adds 10 minutes delay before we update the website, trying to minimize chance of failure.
nex3
commented
10 months ago
We have hit this issue multiple times in the past. While there is a few reports of the same kind of delay, there isn't much technical explanation available.
According to a super old npm blog article from 2014:
The delay is likely that the time taken for each CDN node to replicate the CouchDB metadata containing the package list, and it can take up to minutes. Therefore this PR goes conservative and adds 10 minutes delay before we update the website, trying to minimize chance of failure.
cc @nex3