That doesn't make sense as Node already uses .js for CJS. Tools that assume .js == script already incompatible with all npm
1: People can opt in to modules in package.json if they're using TS or Flow. I'm also fine with "use modules" as an escape valve for
-
-
Defense of .js is well thought out, but was not chosen over Unambiguous nor .mjs
-
"it was not chosen" != "It was not better". Just means the powers that be didn't choose it.
End of conversation
New conversation -
-
-
2/2: standalone scripts. It just doesn't wash to say that .js has only ever meant <script> given node, or only CJS given web.
-
Do browsers ever run .js alone somehow without HTML?
-
Yeah. importScript
-
Doesnt html have to start the worker though? It never stands alone
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.