Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
According to the
Apps that wish to continue using the native
This change should reduce the pain of Windows developers who have had trouble installing a working compiler toolchain to rebuild the native
According to the README, this implementation is approximately 2.7 times slower than native: https://www.npmjs.com/package/bcryptjs Apps that wish to continue using the native bcrypt package should run `meteor npm install --save bcrypt` in the root application directory, and the npm-bcrypt package will prefer that implementation.
You're right! For new hashes, you can pick whatever constant factors you want to make the hashing as slow as you like. But it's still worth noting that there are lots of old hashes out there already, and you can't just recompute them, since that might require unknown information like salts and passwords. So a really big performance difference would not be something we could hide. In this case, 2-3x seems tolerable, and you can always install
I also receive this warning in production after using
I also tried to manually install
In my package.json:
I do run
I am building on OS X 10.11.3 and deploying to CentOS 6. In the deployment, I do an