There are minor ambiguities but they're the rub.
-
-
Replying to @wycats @AdamRackis and
Finding it really hard to let edge case ambiguities warrent an extension change.
2 replies 2 retweets 12 likes -
Replying to @TheLarkInn @wycats and
We are literally able to determine 99.9% of cases accurately and that .01% those users have changed what was really hacky hack code.
2 replies 1 retweet 4 likes -
Replying to @TheLarkInn @wycats and
And there are workarounds for that 0.01% -> add `export default null;` and done.
2 replies 0 retweets 4 likes -
-
-
Replying to @wycats @AdamRackis and
If it lands in spec we could land it in Node
2 replies 0 retweets 0 likes -
Replying to @bradleymeck @wycats and
Do we need to join the drawing board?
1 reply 0 retweets 0 likes -
-
Replying to @bradleymeck @TheLarkInn and
I mean, we can still ship .mjs and "use module" after if still desired and standardized.
1 reply 0 retweets 0 likes
Replying to @bradleymeck @TheLarkInn and
We don't think it should be mandatory but ok in ambiguous contexts.
9:53 AM - 11 May 2017
0 replies
0 retweets
1 like
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.