mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
c3881579ae
Adding native `bcrypt` to a project may require build tools be available on the system. This commit adds a note about that, and a link to the node-gyp documentation that best explains which tools to install. For more details, see this issue: https://github.com/meteor/meteor/issues/10113
41 lines
1.3 KiB
JavaScript
41 lines
1.3 KiB
JavaScript
var assert = require("assert");
|
|
|
|
// The bcryptjs package has a slightly larger API than the native bcrypt
|
|
// package, so we stick to the smaller API for consistency.
|
|
var methods = {
|
|
compare: true,
|
|
compareSync: true,
|
|
genSalt: true,
|
|
genSaltSync: true,
|
|
getRounds: true,
|
|
hash: true,
|
|
hashSync: true
|
|
};
|
|
|
|
try {
|
|
// If you really need the native `bcrypt` package, then you should
|
|
// `meteor npm install --save bcrypt` into the node_modules directory in
|
|
// the root of your application.
|
|
var bcrypt = require("bcrypt");
|
|
} catch (e) {
|
|
bcrypt = require("bcryptjs");
|
|
console.warn([
|
|
"Note: you are using a pure-JavaScript implementation of bcrypt.",
|
|
"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. You may also need to",
|
|
"install build tools to compile bcrypt. For more information see:",
|
|
"https://github.com/nodejs/node-gyp#installation"
|
|
].join("\n"));
|
|
}
|
|
|
|
exports.NpmModuleBcrypt = {};
|
|
Object.keys(methods).forEach(function (key) {
|
|
assert.strictEqual(typeof bcrypt[key], "function");
|
|
exports.NpmModuleBcrypt[key] = bcrypt[key];
|
|
});
|