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
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.
Unfortunately so. But just because we can import conditionally, doesn't mean we have to. This isn't about building nice parsers. For me, this is about easily understanding what my code is doing.
import() is equivalent to require() in terms of static analysability. 90% of the time it works fine. Hence why browserify was even possible. Personally I would encourage all codebases to remain analysable because it enables optimized bundling.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.