npm config set prefix cant read property get of undefined

The most noticeable thing is spending ~200ms on a single one of our dependencies (which, in the case of npm prefix -g is not necessary).īut the way that stuff is factored right now makes it fairly tricky to lazy-load: not impossible, but one of us needs to spend Actual Time on it. It is not a high priority right now, but we've definitely been looking at what exactly is causing the slowdown, and it's a mixture of several things.

If there is any further profiling or debugging to do, I would love to get to the bottom of this. I understand that the original issue was when using nvm, but since it was specifically the npm command that took extremely long, I came here to figure out why. shell: zsh (but similar problems also occurred when using bash).Fresh installs of nvm haven't changed anything, the slowdown is still there. Unfortunately, this is a new machine and this problem has been happening from the first time I installed npm using nvm. How can the CLI team reproduce the problem? I was chasing this issue in nvm-sh/nvm#1261 where nvm was taking incredibly long to load, and then realised that it was just the npm config get prefix command that was responsible for 95%+ of the slowdown. Npm config get prefix takes incredibly long.

Npm config set prefix cant read property get of undefined