JavaScript modules now work in all major browsers, and Node.js has experimental support!
It’s now possible to run the exact same modules, in the exact same files, both on the web and on Node.js.
pic.twitter.com/RLJMA4CoHn
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
I know, I'm just sad the "has import/export? then ESM" idea fell through in the end
I think the goal there was avoiding having to parse the whole file before knowing how to do the module loading.
too bad as soon as you need an entry point that is **not** a module the .mjs extensions becomes absolutely useless and misleading
I also didn't like much your "use the experimental flag" propaganda when the current NodeJS modules status is everything but finalized. 
Agree - as a developer, I do need to know what I'm importing, and so it could be just `import` vs `require` instead ;)
Yes, that's why you should import them differently. ;-)
The much more common case (should) be that a file is a module and not a script. Just because scripts came first, doesn’t mean they should extension squat on .js Dev expierence is paramount and introducing a new extension is a heavy weight tool. Not parsing == simpler != better
That hasn't been an issue for the past 5-6 years as everyone has worked with modules waiting for browser support....
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.