npm update check failed

问题:

Last night I tried to update my node and npm, it seemed to have been successful, however ever since then I have been getting this same error any time I try and run any npm command.

I have tried uninstalling and re-installing npm, but cannot get past this error message below.

Node version: v8.3.0

Error message I am getting:

┌───────────────────────────────────────────────────────────────────┐
│                      npm update check failed                      │
│                Try running with sudo or get access                │
│               to the local update config store via                │
│ sudo chown -R $USER:$(id -gn $USER) /Users/veritystothard/.config │
└───────────────────────────────────────────────────────────────────┘
module.js:491
    throw err;
    ^

Error: Cannot find module 'proto-list'
    at Function.Module._resolveFilename (module.js:489:15)
    at Function.Module._load (module.js:439:25)
    at Module.require (module.js:517:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/config-chain/index.js:1:79)
    at Module._compile (module.js:573:30)
    at Object.Module._extensions..js (module.js:584:10)
    at Module.load (module.js:507:32)
    at tryModuleLoad (module.js:470:12)
    at Function.Module._load (module.js:462:3)

I'm not sure what other details to include here, if anyone has had this issue before I'd appreciate your help. Thanks!

回答1:

Following is the answer from github

Fix for windows, I got this message :

npm update check failed Try running with sudo or get access to the local update config store via sudo chown -R $USER:$(id -gn $USER) C:\Users.config

so I went on to C:\Users.config and deleted the "configstore" folder. once I done this, next time a ran npm start, the folder was re-generated, and error stopped

回答2:

If your are on macOS, you must update the config file. You just have to enter this command in your terminal:

sudo npm i -g npm

回答3:

I have similar error after node updating so i just delete directory .config and this help.

回答4:

I had the same issue on AWS server, i used this command to update the config permissions and the npm command worked smooth.

sudo chown -R $USER:$(id -gn $USER) ~/.config

回答5:

Try running the command prompt Run as administrator mode, if that not solved your issue delete the .config folder under c:\user\<name of the user>\ and then try running the command prompt Run as administrator mode.

回答6:

I had the same error (npm update check failed) on a Centos 7 but not when installing node, just when loggin into the server and it was because there was no more space left. Deleted some files, updated the system and everything worked fine again.

Just in case somebody else comes to the same problem.

回答7:

If you don't want to chown your entire .config directory (which contains configuration files from other programs), try:

sudo chown -R $USER:$(id -gn $USER) "/home/skaestle/.config/configstore/"

回答8:

Run below command from a command prompt

Step 1 : (If possible open cmd as administrator) - npm install -g npm-check-updates

Step 2 : - Open new command prompt and Create a new project

回答9:

I got a Windows 10 environment:

For me, first I did make sure all node.exe instances killed:

taskkill /t /f /im node.exe

Then I've updated npm to the latest version using npm-check-updates

Finally, I deleted .config folder from user home C:\Users\<USERNAME>

That's solved my problem.

回答10:

worked for me after running below command

nvm use --delete-prefix version

回答11:

I have a fixed that worked for me on OSX Catalina:

-------------------------------------
/var/log/nodejs/nodejs.log
-------------------------------------
> node server.js

€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”
│             npm update check failed              │
│       Try running with sudo or get access        │
│       to the local update config store via       │
│ sudo chown -R $USER:$(id -gn $USER) /tmp/.config │
└──────────────────────────â”

I ran the following code in the terminal and as suggested here: sudo chown -R $USER:$(id -gn $USER) /tmp/.config & redeployed to my instance which still showed a degraded state.

I did this several times and this did not result in success.

Since I had a duplicate instance that was in the ready, so I didn't think it was a permissions problem on my local machine.

The following fix worked for me (please note that my code is deployed to ebs through AWS CodePipeline":

1. Delete package-lock.json from your express/node project.
2. Run npm i
3. git add && git commit -m "your commit msg" && git push

In your aws console, go to code pipeline and verify your code deployed successfully.

Navigate to Elastic Beanstalk. If your code pushed successfully, you should see your instance updating.

After this the state of your EBS environment should be in the ready state.

Hope this helps someone out.

回答12:

Running the cmd with admin rights once was enough for me. Just did npm version.

After that it worked again also without admin rights. I did not delete anything.

{
  npm: '6.13.6',
  node: '12.14.1',
  ...
}

回答13:

run script to check for update

sudo npm install -g npm-check-updates

and later update using sudo npm