If you feel you can come up with a better solution for module syntax ambiguity please feel free.
Over the last three years we (including hundreds of devs like you who come in guns blazing calling us all idiots) haven't been able to come up with something that works better.
Proposing or fixing a bug in a third party product should not affect a web standard. If you want my personal help to assist the NodeJS fix, yeah, I would be good there, but I can’t fix the toxic bikeshed culture that you obviously enjoy. MJS is NodeJS solution. It is not a web solution.
You could support .es file types which would work just as well and is more succinct than .mjs, but AFAIK the group won’t because of “branding” issues. Bull. Use .es. Standard semantics for ECMSScript which is the name of the language, no games or pretence.
Over the last three years we (including hundreds of devs like you who come in guns blazing calling us all idiots) haven't been able to come up with something that works better.