So that would mean when Twitch updates the Player/Embed JS, your whole project breaks?
It would only break if the old library version is not supported/available anymore. I’m expecting that when a new version is released, the old one will still be supported for some time, but I see your point.
Whereas if you used the CDN version and wrapping the functions, it would mostly remain working?
This is only true if the interface of the library doesn’t change. If the new library version has a different interface, the typing files will still need to be manually updated.
I fully get your points and I know this is a disadvantage for this approach.
I’ll just expand a bit on my previous point. I think that in Angular, if you’re new to web development, it’s not the easiest thing to include a CDN JS script. Most people are used to npm install x and that’s it, so that’s why I thought having it this way would be more useful.