You still process the resulting JS files in some way, e.g. - minify, set correct mime type on server etc.
-
-
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 -
I'll give you that .es6 for us broke a few tools like Istanbul
1 reply 0 retweets 3 likes -
There were a lot of new extensions initially, `.es6`, `.jsx`, .babel`. Happy that it's now just `.js`
1 reply 0 retweets 3 likes
STRONG CONFIRM.
-
-
1JS yo
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.