7 ms·
The reason I care is because effectively node is imposing it's standards on the browser. Effectively node is requiring all browser based modules to use .mjs eve
by tokyodude 8y ago
The reason I care is because effectively node is imposing it's standards on the browser. Effectively node is requiring all browser based modules to use .mjs even though they shouldn't have to care. Except they will care because they'll start with .js, the make an npm package, then someone will want it to run in node, then it has to be renamed .mjs, then all non node projects are effected only because of node's chosen solution. It seems bad to me for node to effectively bleed it's problems on the entire JS ecosystem