Also it's been around for ages. Literally every tool supports it
-
-
People are stating only one file ext is supported in their tool, .js as a Script
2 replies 0 retweets 0 likes -
Replying to @bradleymeck @satya164
That doesn't make sense as Node already uses .js for CJS. Tools that assume .js == script already incompatible with all npm
1 reply 1 retweet 2 likes -
Would somewhat agree, but decent amount of legacy or side effect only script dont care. Auto strict however...
1 reply 0 retweets 0 likes -
Replying to @bradleymeck @satya164
var x = 1 not creating a global is a MASSIVE diff with scripts. Breaks every script I wrote in 2007.
2 replies 0 retweets 1 like -
No, but auto strict and lack of early return certainly can be
1 reply 0 retweets 0 likes -
-
Saying ESM and CJS differ in ways that are problematic
1 reply 0 retweets 0 likes -
Replying to @bradleymeck @satya164
Right, but CJS and script do as well. The .js extension has always been broad. Never implied semantics just "some kind of JS"
2 replies 0 retweets 0 likes -
The reason node wants .mjs is not a new problem about diff semantics and the meaning of .js. It's about solving a problem Node has.
3 replies 1 retweet 2 likes
iow .js has always meant CJS *in node* and now we need to disambiguate. .js *has not* meant that ecosystem wide.
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.