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
The name of the "node" executable has changed to "nodejs."
(npm even conveniently tells you that this is the problem -- still, the package is broken until it gets fixed)
jwatte@ubuntu:/usr/local/src/project$ npm install keygrip
npm http GET https://registry.npmjs.org/keygrip
npm http 304 https://registry.npmjs.org/keygrip
> [email protected] install /usr/local/src/matchmake/node_modules/keygrip
> node ./install.js
sh: 1: node: not found
npm ERR! error installing [email protected]
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
npm WARN /usr/share/doc/nodejs/README.Debian
npm WARN
npm ERR! [email protected] install: `node ./install.js`
npm ERR! `sh "-c" "node ./install.js"` failed with 127
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the keygrip package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls keygrip
npm ERR! There is likely additional logging output above.
npm ERR!
npm ERR! System Linux 3.8.0-29-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "keygrip"
npm ERR! cwd /usr/local/src/matchmake
npm ERR! node -v v0.6.19
npm ERR! npm -v 1.1.4
npm ERR! code ELIFECYCLE
npm ERR! message [email protected] install: `node ./install.js`
npm ERR! message `sh "-c" "node ./install.js"` failed with 127
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /usr/local/src/matchmake/npm-debug.log
npm not ok
The text was updated successfully, but these errors were encountered:
The name of the "node" executable has changed to "nodejs."
(npm even conveniently tells you that this is the problem -- still, the package is broken until it gets fixed)
The text was updated successfully, but these errors were encountered: