This repository was archived by the owner on Aug 11, 2022. It is now read-only.
This repository was archived by the owner on Aug 11, 2022. It is now read-only.
Intermittent EPERM issues when renaming Windows files during install #12059
Description
On npm@2.14.20:
2016-03-25T00:12:37.6515576Z npm ERR! Windows_NT 6.3.9600
2016-03-25T00:12:37.6515576Z npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
2016-03-25T00:12:37.6515576Z npm ERR! node v4.4.0
2016-03-25T00:12:37.6515576Z npm ERR! npm v2.14.20
2016-03-25T00:12:37.6515576Z npm ERR! path D:\npm-cache\mkdirp\0.5.1\package.tgz.1638249806
2016-03-25T00:12:37.6515576Z npm ERR! code EPERM
2016-03-25T00:12:37.6515576Z npm ERR! errno -4048
2016-03-25T00:12:37.6515576Z npm ERR! syscall rename
2016-03-25T00:12:37.6515576Z npm ERR! Error: EPERM: operation not permitted, rename 'D:\npm-cache\mkdirp\0.5.1\package.tgz.1638249806' -> 'D:\npm-cache\mkdirp\0.5.1\package.tgz'
2016-03-25T00:12:37.6515576Z npm ERR! at Error (native)
2016-03-25T00:12:37.6515576Z npm ERR! { [Error: EPERM: operation not permitted, rename 'D:\npm-cache\mkdirp\0.5.1\package.tgz.1638249806' -> 'D:\npm-cache\mkdirp\0.5.1\package.tgz']
2016-03-25T00:12:37.6515576Z npm ERR! errno: -4048,
2016-03-25T00:12:37.6515576Z npm ERR! code: 'EPERM',
2016-03-25T00:12:37.6515576Z npm ERR! syscall: 'rename',
2016-03-25T00:12:37.6515576Z npm ERR! path: 'D:\\npm-cache\\mkdirp\\0.5.1\\package.tgz.1638249806',
2016-03-25T00:12:37.6515576Z npm ERR! dest: 'D:\\npm-cache\\mkdirp\\0.5.1\\package.tgz',
2016-03-25T00:12:37.6515576Z npm ERR! parent: 'ssb2b' }
2016-03-25T00:12:37.6671853Z npm ERR!
2016-03-25T00:12:37.6671853Z npm ERR! Please try running this command again as root/Administrator.
2016-03-25T00:12:37.6671853Z npm ERR! Please include the following file with any support request:
2016-03-25T00:12:37.6671853Z npm ERR! D:\work\4\s\npm-debug.log
npm-debug.log is here. This was an npm install --force with an empty cache directory (as the debug log shows), but clearly that did not help this time.
Clearing the cache sometimes helps, but just as often it will fail again on some package (not always the same one).