I don't understand what actual concrete benefit there is to using .mjs on client-side JavaScript modules. It seems to only cause problems with tools that .js completely avoids. What's the specific upside?
-
-
If you’re willing to jump through configuration and mental model hoops, feel free to use a different extension. I think avoiding the hassle is a fair recommendation and a sensible default.
-
I don't understand what hoops you're describing. Ember apps have used .js for modules for 5 years. It doesn't make sense to me to introduce churn into my ecosystem for these abstract reasons.
End of conversation
New conversation -
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.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.