Really I think there’s two benefits to using .mjs ext - 1> Understanding what you’re working on in development 2> it follows the node.js experimental module pattern.
“All tooling already deals w this ambiguity.” Exactly, through additional configuration!https://twitter.com/mathias/status/1096035892899266560 …
-
-
I understand the issue deeply, same as you. You’re discounting the additional config required for .mjs. I’m not even arguing against it. Just saying there was an incremental solve not chosen. If the solve involves getting ietf involved, it’s likely the more complicated one.
-
Discussions are interesting because there has not been only 1 configuration mechanism for a long time, but configuration that doesn't overlap is easy to move on/sort out other issues. For some reason people think 1 path is the best path & if we take one path other paths close.
- 2 more replies
New conversation -
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.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.