how to resolve rename error when insalling grunt via npm without admin access?

I need to install grunt for a project setup in Windows 7. However, I am running into an issue that whenever I try to install grunt globally, it fails because of a permission error.

A few other people had this problem and a few others do not, the error that comes up is

EPERM: operation not permitted, rename (insert npm global module path here)\grunt\node_modules\grunt-legacy-log-utils' -> '(insert npm global module path here)\grunt\node_modules\.grunt-legacy-log-utils.DELETE'

Asking for admin permissions to install software is not allowed where I am at.

Answer

Turns out the error was resolved by repeatedly doing npm cache clean and npm install.

Also we also had an issue with node-sass because it couldn’t reach github to download a binary.

Attribution
Source : Link , Question Author : user3346931 , Answer Author : user3346931

Leave a Comment