![]() ![]() The default paths are based on the %AppData%\Roaming path so typically end up as: c:\Users\YOUR_USER_NAME\AppData\Roaming\npmĬ:\Users\YOUR_USER_NAME\AppData\Roaming\npm-cache There are two folders, one for npm prefix folder which is the global install location and another for a cache of packages retrieved from the internet. I turns out that the default install location for npm is in the running users AppData folder. ![]() Sometimes a simple cache clear like the below would fix it, but other times it was more stubborn. Npm install was failing the build intermittently when run by our build software Teamcity on a windows agent with ugly errors like: npm ERR! Error: EPERM: operation not permitted TL/DR The combination of McAfee Anti-virus and network mounted user AppData folders was the culprit - moving them to an unscanned local folder fixed it. The npm install step in my Teamcity CI build for an angular app I have been working has been failing intermittently and I finally uncovered the reason. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |