I believe Node.js leadership is not qualified to make the .mjs decision. Let the community vote with what they use!https://twitter.com/wycats/status/736972528942383104 …
-
-
communication remains an Achilles heel of Node, it is a full-time job to synthesize discussions + context.
-
FWIW, as a CTC member, I lean mjs, but my desire would be to revisit the module spec to remove the sideband req.
-
however my fear is that the spec is immovable and will be cemented by shipping in browsers this year.
-
Has anyone explained plain English why dual parse can't work? Ie, why zero import/export can't just === parse "old school" cjs
-
Of course a small minority of modules w/o export/import - I imagine an export default null; could be palatable workaroud
-
but I'm sure powers that be thought of that - has anyone translated from Spec to plain English what the greater problems are?
-
I don't expect you to write it up for me - just hoping someone has already.
-
cc
@bradleymeck for all ink spilled, hope someone's spelled out rationale in way exper. JS devs who maybe haven't quite read spec can grok - 1 more reply
New conversation -
-
-
noted, but there are other politics at play too, fwiw
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.