Home/ Questions/Q 914
Answered
Kenil Vasani
Kenil Vasani

Kenil Vasani

View Profile
  • 4
Asked: 2020-12-19T22:00:30+00:00

npm update check failed

  • 4

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!

node.jsnpm
Share

    1 Answer

    1. Kenil Vasani

      Kenil Vasani

      View Profile
      Best Answer

      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

      Fix for OSX:

      After two hours of try-and-fail I managed to solve the issue as follows:

      1. go to folder /usr/local/lib/node_modules/
      2. right-click on the folder node_modules > go to Get Info
      3. update the permissions > add yourself and administrator account and set “read and write” for both
      4. run in the terminal “npm install packageName”
      5. if you still get the error, go to the same folder /usr/local/lib/node_modules/ and within the folder node_modules, update in the same way the permissions for the new package folder
      6. try to run again in the terminal “npm install packageName”

      That worked for me! Hope it could help somebody.

      • 3

    You must login to add an answer.