Unpkg CDN down causing dependent website outages
1–10 of 39 posts
Re: Unpkg CDN down causing dependent website outages
#2Re: Unpkg CDN down causing dependent website outages
#3There is also a tool to simplify migration https://www.jsdelivr.com/unpkg
Re: Unpkg CDN down causing dependent website outages
#4I invite everyone affected to consider switching to a production focused CDN https://www.jsdelivr.com/ There is also a tool to simplify migration https://www.jsdelivr.com/unpkg
Re: Unpkg CDN down causing dependent website outages
#5Depend on external services, die by external services. If you can’t afford redundancy, then you must accept downtime.
I build all of my dependent libraries locally and bundle with my app. For one application, I maintain and build the entire OS from source. I depend on aws,azure cloud storage for my own hosted cdn. I can fail back to my own hosts if necessary.
Re: Unpkg CDN down causing dependent website outages
#6I invite everyone affected to consider switching to a production focused CDN https://www.jsdelivr.com/ There is also a tool to simplify migration https://www.jsdelivr.com/unpkg
I invite everyone (even those not affected in this instance) to consider switching away from relying on random third parties for your hosting. Like wtf how is did this ever become the norm even when there was a slight performance advantage from a shared cache, which doesn't even exist anymore these days.
Re: Unpkg CDN down causing dependent website outages
#7in the strictest sense, unpkg is not a cdn. unpkg is a javascript library hosting service that uses cloudflare as a cdn. cloudflare is not down, therefore this headline "unpkg cdn down..." reads as a massive "oh shit!" to infra/devops type cloudflare customers who then have to immediately worry that their site is down, only to realize no, they're fine, this is just devs using the term to mean a different thing (roughly: "third party javascript host").
Re: Unpkg CDN down causing dependent website outages
#8Earlier quoted context omitted.
I invite everyone (even those not affected in this instance) to consider switching away from relying on random third parties for your hosting. Like wtf how is did this ever become the norm even when there was a slight performance advantage from a shared cache, which doesn't even exist anymore these days.
I do both. If you are loading a JS lib then check for its existence on the client. If it's not found load the resource from your server. You could also achieve this on the server side.
Re: Unpkg CDN down causing dependent website outages
#9I assume the developers who use a free third party service for serving their dependencies are the same devs who :pikachu_face: when they are told they can’t statically link GPL libraries into their proprietary apps.
Re: Unpkg CDN down causing dependent website outages
#10I would have thought the risks from 3rd party production dependencies would make devs do all in their power to minimize them. But IIUC it's a somewhat common practice.
Is there something about the market dynamics that make this a reasonable tradeoff? E.g., the problems are rare and this somehow allows faster time to market?
(Asking as a systems programmer, very much not a web developer.)