When we are doing a build, we expect that to be successful.
Although in some cases, we may have momentary network issues or even the project not being able to respond in expected.
Solution
To overcome this scenarios, this PR introduces the concept of retries.
It is configured with 5 retries that are delayed between 1 and 8 seconds.
This was inspired on gatsby-source-graphql implementation since we are already using it, so we can just include node-fetch as peer dependency (correct me if I am wrong).
PS: Not sure why there's many changes on pnpm-lock.yaml but probably because of pnpm version. I am using 8.6.2
Motivation
When we are doing a build, we expect that to be successful. Although in some cases, we may have momentary network issues or even the project not being able to respond in expected.
Solution
To overcome this scenarios, this PR introduces the concept of retries. It is configured with 5 retries that are delayed between 1 and 8 seconds.
This was inspired on
gatsby-source-graphqlimplementation since we are already using it, so we can just includenode-fetchas peer dependency (correct me if I am wrong).PS: Not sure why there's many changes on
pnpm-lock.yamlbut probably because of pnpm version. I am using 8.6.2