> The alternative to CDNs is to use npm and have a build step for your projects. I find this reduces my productivity at hacking on individual tools and makes it harder to self-host them.

No. You can vendor these scripts & host them 1st party so you aren’t leaking data to these CDNs or risk users not actually getting the scripts. It isn’t like CDNs give you a performance boost anymore.

https://httptoolkit.com/blog/public-cdn-risks/

▲

simonw 13 hours ago | parent | next [-]

I wish vendoring was less of a hassle.

I'll vendor and self-host for my professional projects, but for these small experimental utilities I've stopped caring.

	▲	toastal 12 hours ago \| parent [-]
		> small experimental utilities This is what CDNs should be used for at this time—or for fetching the scripts to vendor. That’s fine, but recommending I don’t think is the best call since one folk’s experimental utility will inevitably get released into production—often not even at fault of the utility’s maker. When I use CDNs like this, there are <!-- WARNING … --> around the code just in case someone were to run with it, along with adding the integrity attribute.

▲

chrisweekly 13 hours ago | parent | prev [-]

Great link.