this is difficult: auto strict mode compounds the problem, but the automatic introduction of module scope reqs upfront info
-
-
Replying to @isntitvacant @ag_dubs
then let's send someone to tc39 to make the point that strict mode modules is a deal breaker.
2 replies 0 retweets 1 like -
unforch it wouldn't be enough, even still. we'd need non-top-level {im,ex}port also so we could safely use our module wrapper
1 reply 0 retweets 0 likes -
I'm coming around to the idea that dropping auto-strict (and allowing early return) would alleviate the need for sideband info
1 reply 0 retweets 1 like -
mostly, a few keywords to not be reserved https://tc39.github.io/ecma262/#sec-future-reserved-words … and need to be able to change `this` value
1 reply 0 retweets 0 likes -
Replying to @bradleymeck @isntitvacant and
which pretty much removes a lot of the module goal's ... goals
1 reply 0 retweets 0 likes -
how important is 'this' to node modules? I dont get the impression many rely on it.
1 reply 0 retweets 0 likes -
node's `this === module` in CJS modules, ES modules have `this === global`. I can dredge up people using `this`
1 reply 0 retweets 0 likes -
right, but this==module feels within the limits of reasonable breaking change. Auto strict not so much.
2 replies 0 retweets 0 likes -
might be, just putting everything on the table.
1 reply 0 retweets 1 like
22 references of "this" in the Node module docs, none are about JS `this` https://nodejs.org/api/modules.html …
-
-
Replying to @yoshuawuyts @bradleymeck and
lack of documentation doesn't mean it's ok to break. De facto commitments are commitments.
1 reply 0 retweets 0 likes -
Replying to @izs @yoshuawuyts and
that said, I don't think it's a widely relied upon API feature, but that's a testable claim
0 replies 0 retweets 1 like
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.