npm update check failed

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

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

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

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

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/"

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.

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.

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.

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.

worked for me after running below command

nvm use --delete-prefix version

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',
  ...
}

If the user does not have sudo rights in a unix environment, remember the user name you want to issue the command with (-> USER). Then use

su

Enter your root password. Then

chown -R USER:USER .config

Other .config folders that were created using root are also changed. In my case changing ~/.config/nvws owner did the job (chown -R THE USER YOU USE NPM WITH:THE USER YOU USE NPM WITH .config/nvm)

I'm a windows user. I solved mine by going to the /Users/<username> right clicking the .config folder then in properties un-ticked the read only and apply

This issues come due to TWO reasons

1. You have no permission to read-write
2. Due to window settings folder is secured.

case 1st- just enable the read-write permission case 2nd- if u have permission for read-write and still you facing the same issues, it means you system securities reject the request to write the file, because the file location is given in C drive

solution - JUST disable the firewall / Ransomware protection in windows 10. try again you will get the success.

run script to check for update

sudo npm install -g npm-check-updates

and later update using sudo npm