Agreed. We are very aware of this problem but can only fight so many fires, and the tooling, while complex, is at least solving the problem.
-
-
Absolutely. I think that field is going to save us from the .mjs disaster, if it's not already too late
-
It's almost too late. But not too late. As they say: don't die.
-
I really hope we've still got time. Seems like node core is dragging their feet because everyone knows deep down it's a really bad idea.
-
I really hope so. They're touting GitHub adopting .mjs in GitHub pages as some kind of success story.
-
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.
- 11 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.