Closed andreineculau closed 5 years ago
valid possibility, but what i experienced under WSL, is actually a bug like this https://github.com/Microsoft/WSL/issues/14 so i'm closing without fixing
npm ERR! code EACCES
npm ERR! syscall rename
npm ERR! path /home/linuxbrew/.linuxbrew/lib/node_modules/.staging/npm-667c6cc9/node_modules/yargs
npm ERR! dest /home/linuxbrew/.linuxbrew/lib/node_modules/.staging/yargs-602fdb1d
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, rename '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/npm-667c6cc9/node_modules/yargs' -> '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/yargs-602fdb1d'
npm ERR! [OperationalError: EACCES: permission denied, rename '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/npm-667c6cc9/node_modules/yargs' -> '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/yargs-602fdb1d'] {
npm ERR! cause: [Error: EACCES: permission denied, rename '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/npm-667c6cc9/node_modules/yargs' -> '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/yargs-602fdb1d'] {
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'rename',
npm ERR! path: '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/npm-667c6cc9/node_modules/yargs',
npm ERR! dest: '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/yargs-602fdb1d'
npm ERR! },
npm ERR! stack: "Error: EACCES: permission denied, rename '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/npm-667c6cc9/node_modules/yargs' -> '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/yargs-602fdb1d'",
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'rename',
npm ERR! path: '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/npm-667c6cc9/node_modules/yargs',
npm ERR! dest: '/home/linuxbrew/.linuxbrew/lib/node_modules/.staging/yargs-602fdb1d'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/ubuntu/.npm/_logs/2019-09-01T09_06_14_438Z-debug.log
it doesn't on travis because of special permissions, but it does on a vanilla installation
fix is described here https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally