var x = 1 not creating a global is a MASSIVE diff with scripts. Breaks every script I wrote in 2007.
-
-
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 -
Replying to @wycats @bradleymeck
Is there a 0.1% chance that we could solve the plain js vs modules problem without a special extension and without perf penalties?
2 replies 0 retweets 0 likes -
If the grammars didnt collide, probably but this was talked about in Janhttps://github.com/tc39/tc39-notes/blob/master/es7/2017-01/jan-25.md#13iia-proposed-grammar-change-to-es-modules …
1 reply 1 retweet 3 likes -
Replying to @bradleymeck @satya164
Rejecting package.json + "use modules" for standalone files isn't on technical grounds. But that's where we're at.
3 replies 0 retweets 0 likes -
what's the beef with package.json? is there a link that you can pass on
1 reply 0 retweets 0 likes
There are a lot of minutes of CTC meetings. @littlecalculist and I tried to address objections in Defense of .js.
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.