How do you feel about using cdnjs.cloudflare.com?

Question

Any pros and cons of using public CDNs to deliver the libraries you use? With Subresource Integrity in place, it seems to not be a security risk anymore, right?So the only downsides I can think of are the additional DNS lookup and the risk that it breaks if the CDN goes down.How do you feel about it?

aww_dang · Accepted Answer

Cloudflare pops captchas with a 403 for resources in some cases. This can break your site for users. The main document may load, but resources won't. Of course users won't realize this or see the captchas.

myroon5 · Answer

Notable that cdnjs curates only popular libraries. May need an alternative like jsdelivr if not available on cdnjs

iio7 · Answer

This has become a real cancer on the net, using CDNs for everything. Put the stuff you use on your website, that not only eliminates all the extra DNS querying, but it also prevents someone like Cloudflare to track users.I'm running with uBlock Origin and I block ALL third party CDN stuff. If a website cannot figure out how to store content locally, I wont use it!