Dogfooding at scale: migrating cdnjs to Cloudflare’s Developer Platform
- ID
- 9049
- Status
- summarized
- Published
- 30 Jul 2026, 9:00 PM
- Fetched
- 30 Jul 2026, 9:30 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/cdnjs-dev-platform-migration/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 7.0
- Created
- 31 Jul 2026, 4:29 PM
- Tags
- Audience
- developersvibe_codersai_ml_learners
What happened
As of June 23, 2026, cdnjs—the open-source CDN used on ~12% of all websites, serving 108,000 requests/second (9B/day)—now runs entirely on Cloudflare's Developer Platform (Workers, Workflows, D1, Queues, R2, KV, Containers). The migration surfaced platform limits that Cloudflare then addressed. Notably, LLM coding assistants like ChatGPT, Claude, and Cursor keep generating cdnjs URLs because 15 years of training data reference them, making cdnjs still highly relevant despite the rise of bundlers and ESM.
Why it matters
If you build on Cloudflare's Developer Platform (Workers, D1, R2, KV, Containers), this is a real-world stress test at 9B requests/day across 330+ data centers—useful for gauging production readiness. If you use AI coding assistants, expect them to keep emitting cdnjs <script> tags; plan around that rather than fighting it.
Discussion angle
The irony that AI coding tools keep perpetuating cdnjs usage because their training data is saturated with it—does this lock in legacy patterns, and should you standardize on cdnjs URLs in your own AI-assisted workflows for reliability?