Some weeks ago I had repeated issues with npm getting stuck on installs for maybe 20 minutes and finally erroring out, seemingly due to some network issues. I v

Some weeks ago I had repeated issues with npm getting stuck on installs for maybe 20 minutes and finally erroring out, seemingly due to some network issues. I verified that there was no actual problem with my network, and pnpm installed within seconds. Just as I'm typing this comment, I'm waiting for an npm install to complete for like 10 minutes already, on a project with just maybe 20-ish top level dependencies. It's stuck on this line for like 5 minutes: (####⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂) ⠹ idealTree:regjsparser: sill fetch manifest builtin-modules@^3.3.0 It will probably terminate with some kind or error. This will not happen with pnpm or yarn. Even if it does not, the speed of installation with npm is no match for yarn or pnpm. What might take minutes with npm takes seconds with the others. Also earlier today I had to help a team member install some dependencies in a Node project on a Macbook. We were getting all kinds of errors. After much poking around, it turns out we needed to use `sudo` for the install to succeed, and also resolve some version mismatches between some dependencies, but the error messages did not give any clear indication that these were the problems. Yarn and pnpm will usually just work in such situations, and give messages if some minor issue with the install.