This is probably a problem with file ownership being broken by past uses of sudo with global installs. This was fixed in: Release: 6.10.2
The quick fix is:
sudo chown -R $USER ~/.npm
If you are able to update npm to avoid the problem happening again, upgrade npm and then run the chown again one last time to fix any issues from the upgrade itself.
(For the future, text copy-and-paste of the command and errors is more useful than images because it can be searched and used for reproducing problems.)
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.