-
Notifications
You must be signed in to change notification settings - Fork 88
Description
loadDep:path-is-absolute ▀ ╢██████░░░░░░░░░░░░░░░░░░░░╟
bcrypt@1.0.3 install /home/jeff/node_modules/bcrypt
node-pre-gyp install --fallback-to-build
/usr/bin/env: ‘node’: No such file or directory
/home/jeff
├── carrier@0.3.0
├─┬ commander@2.11.0 (git://github.com/visionmedia/commander.js.git#d9abf56c43a93e9584e2e18a9f8fb5af552f738c)
│ └── @types/node@7.0.43
└─┬ winston@0.6.1
├── async@0.1.22
├── colors@0.6.2
├── cycle@1.0.3
├── eyes@0.1.8
├── pkginfo@0.2.3
├── request@2.9.203
└── stack-trace@0.0.10
npm WARN enoent ENOENT: no such file or directory, open '/home/jeff/package.json'
npm WARN jeff No description
npm WARN jeff No repository field.
npm WARN jeff No README data
npm WARN jeff No license field.
npm ERR! Linux 4.4.0-93-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "i" "ircdjs"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! bcrypt@1.0.3 install: node-pre-gyp install --fallback-to-build
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the bcrypt@1.0.3 install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the bcrypt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs bcrypt
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls bcrypt
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/jeff/npm-debug.log