Comparing version 0.7.2 to 0.7.3
@@ -14,3 +14,3 @@ { | ||
"main": "./bcrypt", | ||
"version": "0.7.2", | ||
"version": "0.7.3", | ||
"author": "Nick Campbell (http://github.com/ncb000gt)", | ||
@@ -17,0 +17,0 @@ "engines": { |
@@ -32,5 +32,9 @@ node.bcrypt.js | ||
Windows users should make sure to have at least node 0.8.5 installed and version >= 0.7.1 of this module. | ||
Windows users should make sure to have at least node 0.8.5 installed and version >= 0.7.1 of this module. | ||
`node-gyp` only works with stable/released versions of node. Since the `bcrypt` module uses `node-gyp` to build and install you'll need a stable version of node to use bcrypt. If you do not you'll likely see an error that starts with: | ||
gyp ERR! stack Error: "pre" versions of node cannot be installed, use the --nodedir flag instead | ||
Security Issues/Concerns | ||
@@ -51,2 +55,3 @@ ============= | ||
* For Windows you'll need http://slproweb.com/products/Win32OpenSSL.html installed to the default location of `C:\OpenSSL-Win32` | ||
* Please note that for this to build properly you'll need the Normal version of OpenSSL-Win<arch>, not the Light version. The reason for this is that we need to be able to compile the code using the header files that exist in the Normal version. | ||
* For 64 bit use the 64 bit version and install to `C:\OpenSSL-Win64` | ||
@@ -61,3 +66,3 @@ * `node-gyp` | ||
npm install bcrypt | ||
npm install bcrypt | ||
@@ -70,9 +75,8 @@ | ||
``` | ||
git clone git://github.com/ncb000gt/node.bcrypt.js.git | ||
cd node.bcrypt.js | ||
node-gyp configure | ||
node-gyp build | ||
``` | ||
git clone git://github.com/ncb000gt/node.bcrypt.js.git | ||
cd node.bcrypt.js | ||
node-gyp configure | ||
node-gyp build | ||
Note: if you do not have node-gyp installed, install it using: `npm install -g node-gyp` | ||
@@ -79,0 +83,0 @@ |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Non-existent author
Supply chain riskThe package was published by an npm account that no longer exists.
Found 1 instance in 1 package
87245
244
0
2