There is eco-system cost and developer cost. I'd say with mjs they are both quite small. Not hearing strong arguments against IMO
-
-
Except when you dont have package.json or your tool doesnt deal with package.json yet. Have to add support.
-
If your tool doesn't support package.json it won't have known about CJS.
-
Tools that don't know about package.json prolly aren't working too well with Node anyway! :)
- End of conversation
New conversation -
-
-
Not being able to `import` with standalone files / in CLI seems like a pretty reasonable tradeoff to make. & can still be require'd, right?
-
require() still works + we could add new top-level executable or pragma, yeah.
-
Great. If you choose to operate without package.json, then you can use old require syntax. Why not optimize for app development?
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.