Tools already support the .js extension, prism.js will still highlight the file correctly without any configuration for example
-
-
There is eco-system cost and developer cost. I'd say with mjs they are both quite small. Not hearing strong arguments against IMO
2 replies 0 retweets 0 likes -
What's the point of the cost at all if it could be avoided?
2 replies 0 retweets 0 likes -
None of th suggestions avoid cost, they just change who has to pay
1 reply 0 retweets 0 likes -
A key in `package.json` and simple and straightforward without having to configure each and every tool, the cost is negligible
3 replies 0 retweets 0 likes -
Doesn't solve local files.
1 reply 0 retweets 0 likes -
I'm not sure what you mean, a key in `package.json` does solve local files
2 replies 0 retweets 0 likes -
Sorry like node file.js. I guess we can have a command line option?
1 reply 0 retweets 1 like -
A pragma is a proposed solution for single files, which I think is totally fine.
3 replies 0 retweets 0 likes -
I'll be fine with a CLI parameter too
1 reply 0 retweets 0 likes
We could also create a new top-level `js` that defaults to modules. Narwhal is long gone ;)
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.