If you're using TypeScript does this matter at all? You're still tranpiling. It's a config flag. Is there a greater cost than just renaming?
-
-
You still process the resulting JS files in some way, e.g. - minify, set correct mime type on server etc.
1 reply 0 retweets 0 likes -
If you process them does .mjs impede you more thank package.json or pragma (which is oof in JS)?
1 reply 0 retweets 0 likes -
Still have to configure server to serve correct mimetype for a new extension and configure tools, which is not the case for .js
2 replies 0 retweets 1 like -
.mjs does not impede you shipping .js if you only want web. Also statement of processing files makes me assume you can rename
2 replies 0 retweets 1 like -
We write universal code now-a-days :D Yeah, we can definitely rename, and configure tools. But if it's not really necessary, why do that
1 reply 0 retweets 0 likes -
Configure tools is literally like flipping a config param. Takes seconds...
2 replies 0 retweets 0 likes -
Submitting PRs to every project like pygments, GitHub, highlight.js, prism, etc etc takes more than seconds.
3 replies 0 retweets 3 likes -
And .mjs will likely drift out of sync with .js in the lesser maintained tools, which are widely in use.
2 replies 0 retweets 1 like -
Unclear on this, .js will stay CJS forever in Node ecosystem.
1 reply 0 retweets 1 like
I mean tools like pygments will likely get PRs to update .js but forget .mjs and vice versa. Less maintained tools will forget to replicate
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.