Question About CDN Usage in Web Worker Since v2.0.1

[MaskedHawk]

Hi there,

I hope you're doing well. I've been using your library (v2.0.1) for a while now and I've noticed that it uses a CDN for the web worker, even when I have it installed via npm. I understand that you've mentioned we can host the CDN ourselves if needed, but I'm curious about the rationale behind this design choice.

I have a couple of questions:

Why is the library configured to use an external CDN source for the web worker component, especially when I have it installed locally using npm? What advantages or considerations led to this decision?

Could you please elaborate on the benefits of using a CDN for the web worker part of the library, even in cases where the library is already present locally via npm? Are there performance or reliability reasons that make this approach preferable?

I appreciate your work on this library and would love to gain a better understanding of the reasoning behind this choice. Your insights will help me use the library more effectively and make informed decisions regarding its implementation in my projects.

Thank you for your time and assistance.