@lbljeffmo it's not simple to newly make "CJS or standard" part of the public interface.
@lbljeffmo it changes the public interface of existing modules to include the kind of module, which is not true now and not necessary
-
-
@wycats it is true now -- node doesn't execute ES modules. I only executes CJS modules. Some compile ES -> CJS, but it's still CJSThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@lbljeffmo and it unnecessarily complicates migrations of users of modules that already required with .js -
@wycats it doesn't. Those users work tomorrow just as they do today. They can also actively upgrade (just as they can with either proposal) -
@lbljeffmo if a package moves to .mjs, that breaks their consumers. -
@wycats same as if they move to module.js without compiling for node5/node6 users -
@lbljeffmo .js -> .mjs breaks node7 users; module.js breaks only node5/node6 users. -
@lbljeffmo Some packages wait long enough that they can migrate after they don't have to worry about old nodes anymore -
@wycats neither soltn fixes backward compat. .mjs only works w/ latest node, module.js only works w latest node
End of conversation
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.