It seems odd that I get told tools cannot handle new file extensions but that they will support WASM
-
-
Replying to @bradleymeck
I genuinely don't get what you're saying here. .wasm is a totally new syntax, while .mjs is a superset of a large existing format.
1 reply 0 retweets 0 likes -
Replying to @wycats
Some people are claiming they cannot support multiple extensions *at all*
2 replies 0 retweets 0 likes -
Replying to @bradleymeck @wycats
Not really specific to .mjs, .jsx etc also apply
2 replies 0 retweets 0 likes -
Replying to @bradleymeck @wycats
Also ESM isnt really a superset, it evals diff
2 replies 0 retweets 2 likes -
Replying to @bradleymeck @wycats
.jsx isn't actually recommended anymore and is discouraged, react-native doesn't support the extension for example
2 replies 0 retweets 1 like -
Depends on guide. How about .json then.
2 replies 0 retweets 0 likes -
Though I would say JSX is a superset since without elements code evals the same.
1 reply 0 retweets 0 likes -
Replying to @bradleymeck @wycats
JSX is more like syntactic addition like Flow. But I guess we could consider them supersets, not how it's used in practice though
1 reply 0 retweets 0 likes -
If JS without JSX additions runs with a JSX parser it doesnt change how ops eval or variables, ESM does
1 reply 0 retweets 0 likes
But that's also true about CJS and yet .js is used. Node's position really cannot come from a need to distinguish from <script>
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.