There are minor ambiguities but they're the rub.
-
-
There are _so many_ good options that don't require Node-specific baggage.
-
I'm still not 100% convinced this is entirely node specific as I have stated about non-node platforms affected by ESM
-
Though, I generally get told they either don't matter, they are edge cases, or that they should follow some specific proposal just not .mjs
-
I also am very against package.json, love "use module" though if required for ESM
-
To be clear, I am against the loss of random things or odd fields that are permanent debt
-
How does a new file extension not qualify as exactly that?????
-
Explain how it is debt if no .js files exist in future
-
Plenty of web apps use non-Node backends (we use .net) - hard to imagine .js would ever disappear
- 1 more reply
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.