Modern Script Loading
If you're implementing module/nomodule, this might help clarify the trade-offs and options you have available.
http://jasonformat.com/modern-script-loading/ …pic.twitter.com/a3jVXzGfVY
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Doing this in parallel to Angular's differential loading. In our env it's mostly about IE11 vs others, so checking that first, then serving either ES5 or ES2015 bundle. Works like a charm.
Also "What if your request mismatch the UA" - that doesn't hurt us since two types of bundles have to work properly. There's nothing wrong with the legacy one except it's just bigger.
(As opposed to say, completely blocking website access based on the UA string. Boo to that!)
Also, if you're just sniffing for JS engine level, UA sniffing can be done pretty concisely and generally. Something like the following:https://gist.github.com/domenic/534c1da00ae7d0ed780d3f3d715d4466 …
I wish I could have this on a sticker/shirt/hat/massive-sign. So many people say UA sniffing is inherently bad or wrong. UA sniffing for progressive enhancement and ensuring to avoid false positives is a great use-case for UA sniffing.
I guess "Option 3: UA sinff then inject the entire file" could be optimal since you're saving another request?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.