Some (a lot?) is on node core and the modules story. The .mjs proposal is going to wreak havoc on the FE ecosystem, which uses .js for years
-
-
fwiw I did see Bradley say that .mjs was "written in stone" - which sucks. But hey, just use
@jdalton's loader and move on! -
That's fine. Let them write it in stone. They're just writing themselves into oblivion. FE community (huge majority of npm) won't use it.
-
npm isn't stopping anybody doing anything, and will support whatever the majority end up doing. So far nobody's much of anything.
-
npm attempting to influence the outcome by picking a winner seems like a bad idea, if only because we have no idea what we're doing.
-
At least npm has its finger on the pulse of the whole module ecosystem.
-
We certainly do, which is why I can say with confidence "it is not yet clear which way this is going to go".
-
I very much appreciate npm's willingness to go with the flow
that's how consensus should work! I just predict FE community won't use .mjs -
And given your original poll, that community represents a large portion of npm's user base
- 7 more replies
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.