bcrypt-as-promised | Promises A version of bcrypt | REST library

I found a solution to my issue was to use yarn to import all of my dependencies rather than npm, while also swapping bcrypt-as-promised for bcrypt (which now includes promises with no syntax changes necessary).

1. I ditched bcrypt-as-promised and replaced it with bcrypt in my package.json file.

2. I then changed any instance of require('bcrypt-as-promised') to require('bcrypt') (the syntax for using bcrypt remains the same, just the dependency importation lines need to change).

3. Without using yarn, even after changing my folder permissions, I was still hitting permissions "EACCES: permission denied" errors, with only bcrypt failing. My versions of npm and node seemed fine. Made sure my Ubuntu box was all updated.

4. That's when I gained the suggestion from a wise friend to try using yarn to grab the dependencies instead. I ran yarn import which reads the package.json file and creates a yarn.lock file. I then installed yarn on my ubuntu machine (sudo npm install yarn -g), and ran yarn install, and bcrypt successfully installed!

It looks like if npm dependencies were originally installed using sudo, permission issues can be experienced when trying to install bcrypt. My improved solution was to:

• Nuke the ./node_modules folder via sudo rm -r ./node_modules
• Install npm packages fresh (not using sudo).
• After this, I was able to npm i --save bcrypt with the package installing successfully.

Here's a link from GitHub that helped me find the solution and an excerpt:

@Mayocampo permission denied, mkdir '/home/someroute/node_modules/bcrypt/build'

It seems you run rpm as root, therrfore your account cannot mkdir under /home/someroute/node_modules/ Check dir with ls -l /home/someroute/node_modules/ Im sure owner of upper dir is root. or your account cannot have permission.

I guess there are two options are available.

1. sudo rm -r ./node_modules And install package via npm again, but without using sudo.
2. Change mod ./node_module to access and excutable. I decided first, and its fixed

Source: juicycool92 @ GitHub