While this implementation will work correctly, it is known to be
approximately three times slower than the native implementation.
In order to use the native implementation instead, run
meteor npm install –save bcrypt
in the root directory of your application.
I have seen many people ask about this error on the Meteor forums unanswered. Seems like a simple solution given, but that npm install can also lead an anther error.
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/home/responsive/.meteor/packages/meteor-tool/.1.4.1_3.1159dv8++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 4.4.0-38-generic
gyp ERR! command “/home/.meteor/packages/meteor-tool/.1.4.1_3.1159dv8++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/node” “/home/responsive/.meteor/packages/meteor-tool/.1.4.1_3.1159dv8++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js” “rebuild”
gyp ERR! cwd /home/simple-todos/node_modules/bcrypt
gyp ERR! node -v v4.6.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm ERR! Linux 4.4.0-38-generic
npm ERR! argv “/home/.meteor/packages/meteor-tool/.1.4.1_3.1159dv8++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/node” “/home/.meteor/packages/meteor-tool/.1.4.1_3.1159dv8++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/npm” “install” “–save” “bcrypt”
npm ERR! node v4.6.1
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! email@example.com install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! Failed at the firstname.lastname@example.org install script ‘node-gyp rebuild’.
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-gyp rebuild
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/simple-todos/npm-debug.log
Its an unnecessarily long and complicated way of saying that you version on NodeJS and NPM is not up to date. The solution is easy but not obvious to most NodeJS users.
Leave your project alone and go to the root terminal.
This checks the latest version of NodeJS. Google to see if it matches the latest version.
sudo npm cache clean -f sudo npm install -g n sudo n stable
Then check the new version again. Warnings pop up “I sure hope you know what you are doing.” The answer for me is usually, no but that’s alright.