Agree, but that ship sailed
-
-
Finding it really hard to let edge case ambiguities warrent an extension change.
-
We are literally able to determine 99.9% of cases accurately and that .01% those users have changed what was really hacky hack code.
-
And there are workarounds for that 0.01% -> add `export default null;` and done.
-
`export {}` is a bit better
-
"use modules" is even clearer
-
If it lands in spec we could land it in Node
-
Do we need to join the drawing board?
- 2 more replies
New conversation -
-
-
If package.json main -> module so awful it can't be done, I'd infinitely prefer Node "just" support ESM w/ > 0 import/export.
-
I still think every one is gonna give up on this and stick to CJS. It's like XHTML2 all over again
-
That or fork, and make a version of Node built around ECMA-262, rather than legacy Node stuff.
-
The io.js name is available again ;)
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.