Dynamic `import()` unlocks new capabilities compared to static `import`. Here’s what you should know: https://developers.google.com/web/updates/2017/11/dynamic-import …pic.twitter.com/NulbdCicg7
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
Static `import` enables static analysis. How could a dynamic form of that work with static analysis?
I don't know, and that has hit me before. Who's fork of library X am I using? Is it the same version that is used in production? Is object Y in scope? Why don't my modifications work? Does my import depend on a working DNS resolver? How do I find this out without, "just run it"
Well, you could statically detect if `import()` is used by parsing (precisely because it’s syntax and not a real function). It’s just not always possible to figure out the import specifiers statically, or to determine which of them will even be reached.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.