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
That is, the simplest possible implementation would simply match a hardcoded set of UA strings, and nothing else. You don't need to handle every possible edge case. There's nothing inherently wrong with UA sniffing if it's used as progressive enhancement in this manner.
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.
This makes sense! I will probably add this to the blog post.
Precisely. The key is that the default for something you don't recognise is fallback, and evergreen only gets sent to things you know for sure are good. This is probably the point at which I should plug my article on the approach we took
https://sgom.es/posts/2019-03-06-supporting-old-browsers-without-hurting-everyone/ …
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.