Private NPM Package details not loading on package.json about vscode HOT 8 CLOSED

@aeschli As you mentioned, I tried npm view on the terminal and this is the result

As you can see, npm is accessible, and npm view can locate the package just fine with all the details. This issue is with VS Code and not with npm because everything was working fine 2-3 weeks back before updating VS Code, and I have not updated node or npm in my system.

Also, I see Loading text when I hover over the packages before the tooltip crashes. So, my guess, something is breaking between Loading and rendering the npm view result.

from vscode.

I'm quite sure that this was caused by a recent change. We longer pass in the full environment when running npm
I fixed it with #213306

from vscode.

i have the same issue. previously it worked

from vscode.

We are look for a installed npm command. If we find it, we use it with npm view.

• can you check that npm is on the PATH? whereis npm (on Linux and Mac) where cmd.cmd (on Windows) should find the command
• try npm view @yahaal/ecommerce

If npm is not found, we fall back to an online service which can not load private repos

from vscode.

I am also having the same issue on mac

from vscode.

I also have the same issue, and previously it worked. npm view can work for private registry packages.

And for more information, my npm is managed by fnm as same as node.

from vscode.

I just noticed this same issue too. Just last week I was using it fine when updating our private packages. I ran the npm view command with success like @kalesh13

from vscode.

This has been happening for me for the past couple of weeks as well, but for all my packages (I don't have any private packages installed). I use yarn so I'm not sure if that's affecting the registry values, but npm view works fine. This feature used to work and I haven't changed anything on my end so it's definitely a regression in VSCode.

from vscode.