I'd recommend using CDN when you're just playing around. It's quick & cheap way to experiment but rely on packaging when you're deploying to something of importance (i.e. in production).
Packaging gives you dependency management, source control, static checks / analysis. If the cost of hosting the CDN is too high, then roll your own (or use of them CDN as service tools).
If you're in the corporate world, in either case you'll have to worry a lot more about licensing, source code correctness, security and accessibility of code / CDN.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'd recommend using CDN when you're just playing around. It's quick & cheap way to experiment but rely on packaging when you're deploying to something of importance (i.e. in production).
Packaging gives you dependency management, source control, static checks / analysis. If the cost of hosting the CDN is too high, then roll your own (or use of them CDN as service tools).
If you're in the corporate world, in either case you'll have to worry a lot more about licensing, source code correctness, security and accessibility of code / CDN.