Imagine this: Alex, a diligent developer, is hard at work on a new web application.

Stable Diffusion

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Learn how to create and manage your own library of reusable JavaScript code. Discover the benefits of code reuse and explore popular CDN options for hosting JavaScript libraries.

Code Once, Use Everywhere: A Developer's Guide to Centralizing Custom JS Tools

This way of organizing work is a great solution

I am not sure if CDN is a better alternative or even right alternative to package managers. Even though I appreciate the intent, a utility belt is higly unlikely big enough to make a difference in loading time from a CDN provider. That is why I have doubts if the given example right for the context.
I understand the initial struggles of publishing a package. But it is low maintenance after that. And if you don’t want to other people get involved in your project, simply go premium. I am not sure if the cdn providers are both free and private at the same time.
Nevertheless, a developer should know alternative tools to make the right decision. I am sure CDN is prove its usefulness in other scenarios. I simply don’t get the extra value in given example but I will think about it.