[graphiql] The https://unpkg.com/@graphiql/plugin-explorer/dist/index.umd.js sometimes take a very long time to load

[ssprang]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hi! 👋🏻

This is probably not on you but maybe on unpkg.com ? Not sure how to report to them though..

The last few days it can take up to 12 seconds to load https://unpkg.com/@graphiql/plugin-explorer/dist/index.umd.js which makes the graphiql explorer blank for that amount of time, is it possible to fix it somehow? 😇

Expected Behavior

Usually the graphiql explorer is fast to load.

Steps To Reproduce

1. Open the graphiql explorer for any graphql schema
   a) if it's fast, wait 5 minutes for the cache to expire or clear your browser caches
   b) if it's slow you've encountered the issue

Environment

• GraphiQL Version: latest
• OS: Mac Os
• Browser: Chrome
• Bundler: ?
• react Version: ?
• graphql Version: ?

Anything else?

No response

[ssprang]

This is getting worse..
https://unpkg.com/react@18/umd/react.production.min.js took 90 seconds to load today.. I suspect unpkg has some caching issues, it renders the graphiql explorer unavailable for the time it takes to load these assets.

[stacey-gammon]

unpkg appears to be completely down now?

[ssprang]

Today the graphiql explorer won't load at all, critical resources are getting 520 errors most likely due to cloudflare/server issues for unpkg.

A 520 status code is related to Cloudflare. It is used by Cloudflare as a catch-all response for when the origin server sends something unexpected.

[ssprang]

Looking at the (unfortunately many) unpkg issues, others seems to be abandoning them for other cdns like https://www.jsdelivr.com/ ..

unpkg/unpkg#440
unpkg/unpkg#444

Could the graphiql explorer please consider switching too? 😇

[dimaMachina]

UMD CDN builds are deprecated, use ESM-based CDN instead, check out the migration guide for more info.