core(www): unpkg responds with "Response code 429 (Too Many Requests)"

Description

requesting README from https://unpkg.com/ results in “Response code 429 (Too Many Requests)”

Steps to reproduce

• checkout gatsby
• open https://github.com/gatsbyjs/gatsby/blob/f95cd06bb8454ae3a9dd746f6e4fa3f12bdc3717/packages/gatsby-source-npm-package-search/src/gatsby-node.js#L38-L46
• add line into the catch blog:

console.log(`"${hit.objectID}" - error "${err.message}" `);

• run gatsby develop

Expected result

• it should only print 404 error messages resulting from missing README

Actual result

many times i see the error:

• “Response code 429 (Too Many Requests)”

[arguiot]

I’ve looked on Google for a possible answer and I found that the response on UNPKG: Response code 429 (Too Many Requests) was due to a bug/config problem on CloudFlare which causes the traffic to be redirected to Google Cloud in some situations: https://github.com/mjackson/unpkg/issues/237#issuecomment-568770980

I’m not sure if the issue comes from Cloudflare or UNPKG (honestly I believe this is a problem with UNPKG, but the developer hasn’t spoken on this yet…).

The obvious solution for Gatsby is to use jsDelivr (as I said before). The PR would be super easy to do and it will fix this issue.

[github-actions[bot]]

Hey again!

It’s been 60 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to comment on this issue or create a new one if you need anything else. As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community! 💪💜