Description

Yuvraj102

opened on Apr 8, 2022

Issue body actions

I cloned this repo, cd into the api folder and entered sudo npm install but got a bunch of errors
npm ERR! node-pre-gyp WARN Pre-built binaries not found for [email protected] and [email protected] (node-v93 ABI, unknown) (falling back to source compile with node-gyp)
npm ERR! node-pre-gyp http 404 status code downloading tarball https://github.com/kelektiv/node.bcrypt.js/releases/download/v3.0.6/bcrypt_lib-v3.0.6-node-v93-darwin-x64-unknown.tar.gz
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | darwin | x64
npm ERR! gyp info ok
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | darwin | x64
npm ERR! gyp info find Python using Python version 3.8.5 found at "/opt/anaconda3/bin/python3"
npm ERR! gyp WARN EACCES current user ("yuvrajvijayagarkar") does not have permission to access the dev dir "/Users/yuvrajvijayagarkar/Library/Caches/node-gyp/16.14.2"
npm ERR! gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
npm ERR! gyp info spawn /opt/anaconda3/bin/python3
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args 'binding.gyp',
npm ERR! gyp info spawn args '-f',
npm ERR! gyp info spawn args 'make',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args '/User

I updated my node to 16th version, also npm to 8th version but still issue persists

Activity

1. Yuzeyzer commented on Apr 8, 2022

   

   Yuzeyzer

   on Apr 8, 2022

   More actions

   Same for me... I also installed node-pre-gyp locally and used 14.15.3 node version, but it did not change anyting. Seems like many packages that was used here are outdated.

   Solution: If you will remove bcrypt package from package.json and try once more without bcrypt it will work. You just have to install bcrypt manually by using "npm i bcrypt" it will download latest version without any errors.

   Warning: But be carefull, i am not sure that using latest version of bcrypt good idea here, cause some modules from older bcrypt could be removed/renamed in newer one and you may have problems in future.

   Reacted by Jim
2. Yuvraj102 commented on Apr 14, 2022

   

   Yuvraj102

   on Apr 14, 2022

   Author

   More actions

   Makes me wonder if wether or not I should follow the book @Yuzeyzer
3. Dmtreaqq commented on Jun 2, 2022

   

   Dmtreaqq

   on Jun 2, 2022

   More actions

   the problem is with bcrypt package, which needs python installed on your pc

   I just installed Python from Microsoft store and npm install worked without errors

   Or we need to pick another bcrypt package from npm
   https://stackoverflow.com/a/29320712/12654113
4. PurpleSPC commented on Jul 10, 2022

   

   PurpleSPC

   on Jul 10, 2022

   More actions

   I got this to work for me. I needed to use node version 12.14.1, the current version as of the books publishing. I am using windows 11.
   Try:
   Uninstall node.js

   Install nvm-windows: https://github.com/coreybutler/nvm-windows#installation--upgrades

   In the terminal type nvm install 12.14.1 Followed by nvm use 12.41.1

   then clone the repo and use npm install.
5. aZuh7 commented on Jul 22, 2022

   

   aZuh7

   on Jul 22, 2022

   More actions

   I got this to work for me. I needed to use node version 12.14.1, the current version as of the books publishing. I am using windows 11. Try: Uninstall node.js

   Install nvm-windows: https://github.com/coreybutler/nvm-windows#installation--upgrades

   In the terminal type nvm install 12.14.1 Followed by nvm use 12.41.1

   then clone the repo and use npm install.

   This also worked for me, but a couple notes:

   1. I think you meant nvm use 12.14.1 .
   2. Windows users, make sure you are running your terminal or IDE in administrator mode, otherwise nvm use 12.14.1 will not work.
   3. For some windows users, make sure to navigate to your C:\Program Files or C:\Program Files(x86) directory to ensure the nodejs folder was completely deleted when you uninstalled node.js, otherwise you will get an "exit status 145: The directory is not empty." error when running nvm use 12.14.1.

   Reacted by Hamberfim
6. cstarbird commented on Sep 12, 2022

   

   cstarbird

   on Sep 12, 2022

   More actions

   I ran into the same issue while trying to follow the book on a Debian (bullseye) vm that did not have python installed. I was able to solve it by replacing bcrypt with bcryptjs (latest version) in the package.json. We'll see if it comes back to bite me later, but so far so good.
7. xgqfrms commented on Dec 7, 2022

   

   xgqfrms

   on Dec 7, 2022

   More actions

   this repo's codes need to be updated to keep up with date

   # latest version ❌
   $ node -v
   v18.12.0
   

   # nvm
   $ nvm use 16.18.0
   
   # old version ✅
   $ node -v
   v16.18.0

Issue actions