4 ms·
Npm has lots of not understandable mistakes: it should already be as good with ES6+TS as other systems. Import should just work everywhere. We should have left
by xiphias2 4y ago
Npm has lots of not understandable mistakes: it should already be as good with ES6+TS as other systems. Import should just work everywhere.
We should have left Commonjs a long time ago, while keeping backwards compatibility.
At the same time what I see with the node+npm system is that everything is just ,,it just doesn't work by default''.
Having 10 other package managers doesn't work either, they are faster, but don't solve this problem.
- eurasiantiger 4y agoJust use .mjs extension for your code, add extensions to your imports and everything does just work.
- noahtallen 4y agoExcept in typescript, where you have to import a file with the .js extension, despite the actual file being .ts: https://github.com/microsoft/TypeScript/issues/42151 https://github.com/microsoft/TypeScript/issues/42151, https://github.com/microsoft/TypeScript/issues/49083 https://github.com/microsoft/TypeScript/issues/49083, https://github.com/microsoft/TypeScript/issues/16577 https://github.com/microsoft/TypeScript/issues/16577 This one issue (IMO) is preventing parts of the ecosystem from switching to esm.
- mhio 4y agoHow does the js extension stop a project from targeting ESM?