well actually when you host an SPA and you DO use lazy loading (which you probably need to do on angular, because of sizing, etc...)
than you will run into problem if you don't put all assets into a second webserver that will hold all assets (i.e. all versions).
if you try to deploy these assets directly with your normal application than you will probably run into serious trouble when users that do not have the newest version will try to download these lazy loaded stuff.
> well actually when you host an SPA and you DO use lazy loading
This is not always true. Many times frameworks are so heavily leveraged and the site-specific code so minimal on small SPAs that it is reasonable to have a single packed-and-minimized JS file. And it still may change frequently.
yeah as said, only when you do, but on angular you probably need to do.
however I had good luck with vuejs which basically was relativly small.
I also tend to do lazy loading pdfjs or something really big.
