You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm ERR! enoent ENOENT: no such file or directory, rename '/usr/local/lib/node_modules/.staging/node-pre-gyp-788c79f0' -> '/usr/local/lib/node_modules/grpcc/node_modules/grpc/node_modules/node-pre-gyp'
npm ERR! enoent ENOENT: no such file or directory, rename '/usr/local/lib/node_modules/.staging/node-pre-gyp-788c79f0' -> '/usr/local/lib/node_modules/grpcc/node_modules/grpc/node_modules/node-pre-gyp'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR! /root/npm-debug.log
The text was updated successfully, but these errors were encountered:
I've tried completely deleting everything associated with node and I can not get grpcc to install through rpm at all.
npm version is 3.5.2
node version is 4.2.6
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "grpcc"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! path /usr/local/lib/node_modules/.staging/node-pre-gyp-788c79f0
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/usr/local/lib/node_modules/.staging/node-pre-gyp-788c79f0' -> '/usr/local/lib/node_modules/grpcc/node_modules/grpc/node_modules/node-pre-gyp'
npm ERR! enoent ENOENT: no such file or directory, rename '/usr/local/lib/node_modules/.staging/node-pre-gyp-788c79f0' -> '/usr/local/lib/node_modules/grpcc/node_modules/grpc/node_modules/node-pre-gyp'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR! /root/npm-debug.log
The text was updated successfully, but these errors were encountered: