believe the import keyword will be before; the import function will be at runtime. Keyword can only be used at top level
Wasn't sure what all the ways to import files in node is gonna be, so typed it out. Not sure I got it right 100%, but yeah it's somethingpic.twitter.com/dI51tPXuxm
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
yeah, tho having options is nice and browser symmetry however distasteful is the right thing to do. shame it grew so complex.
-
yeah, with you here - I'll forever think of mmify tho, the module system that could've been https://github.com/substack/mmmify
End of conversation
New conversation -
-
-
@denormalize this is absolutely not our fault -
nobody's blaming anyone; these are just notes on trying to make sense of upcoming stuff (:
@denormalize
End of conversation
New conversation -
-
-
what is import_ ? a typo?
- End of conversation
New conversation -
-
-
Forgot to show that you don't need `import` to do things like: const { exec, spawn } = require('child_process')
-
the import + destructuring conflation... I'm convinced it is part of why many adopted it in the first place
- 4 more replies
New conversation -
-
-
await import('foo') might not work as top level await but probably will in an async fn...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.