>Similar problems with runtime version management (need to use nvm for sanity, using built-in OS package managers seems to consistently result in tears). In pr

>Similar problems with runtime version management (need to use nvm for sanity, using built-in OS package managers seems to consistently result in tears). In practice I find this a nuisance but a small one. I wish there had been a convention that lets the correct version of Node run without me manually having to switch between them. > More package managers and interactions (corepack, npm, pnpm, yarn, bun). But they all work on the same package.json and node_modules/ principle, afaik. In funky situations, incompatibilities might emerge, but they are interchangeable for the average user. (Well, I don't know about corepack.) > Bad package interop (ESM vs CJS vs UMD). That is a whole separate disaster, which doesn't really impact consuming packages. But it does make packaging them pretty nasty. > More runtimes (Node, Deno, Bun, Edge). I don't know what Edge is. Deno is different enough to not really be in the same game. I find it hard to see the existence of Bun as problematic: it has been a bit of a godsend for me, it has an amazing ability to "just work" and punch through Typescript configuration issues that choke TypeScript. And it's fast. > Then compound this all with the fact that JS doesn't have a comprehensive stdlib so your average project has literally 1000s of dependencies. I guess I don't have a lot of reference points for this one. The 1000s of dependencies is certainly true though.