node-pre-gyp - npm Package Compare versions

Comparing version 0.6.26 to 0.6.27

CHANGELOG.md

@@ -5,2 +5,3 @@ # node-pre-gyp changelog
 
+ - Add known node version for node v6
  - Stopped bundling dependencies
@@ -7,0 +8,0 @@ - Documented method for module authors to avoid bundling node-pre-gyp

lib/util/abi_crosswalk.json

@@ -1146,2 +1146,6 @@ {
   },
+  "4.4.3": {
+    "node_abi": 46,
+    "v8": "4.5"
+  },
   "5.0.0": {
@@ -1210,3 +1214,11 @@ "node_abi": 47,
     "v8": "4.6"
+  },
+  "5.11.0": {
+    "node_abi": 47,
+    "v8": "4.6"
+  },
+  "6.0.0": {
+    "node_abi": 48,
+    "v8": "5.0"
   }
 }

package.json

 {
   "name": "node-pre-gyp",
   "description": "Node.js native addon binary install tool",
-  "version" : "0.6.26",
+  "version" : "0.6.27",
   "keywords": [
@@ -6,0 +6,0 @@ "native",

README.md

@@ -15,3 +15,3 @@ # node-pre-gyp
 
- - A command line tool called `node-pre-gyp` that can install your package's C++ module from a binary.
+ - A command line tool called `node-pre-gyp` that can install your package's c++ module from a binary.
  - A variety of developer targeted commands for packaging, testing, and publishing binaries.
@@ -34,3 +34,3 @@ - A Javascript module that can dynamically require your installed binary: `require('node-pre-gyp').find`
 
- - Node.js 0.12.x -> 0.8.x
+ - Node.js >= node v0.10.x
 
@@ -76,3 +76,2 @@ ## Install
  - `--build-from-source`: build from source instead of using pre-built binary
- - `--update-binary`: reinstall by replacing previously installed local binary with remote binary
  - `--runtime=node-webkit`: customize the runtime: `node`, `electron` and `node-webkit` are the valid options
@@ -98,3 +97,3 @@ - `--fallback-to-build`: fallback to building from source if pre-built binary is not available
 
- - Add `node-pre-gyp` to `dependencies`
+ - Add `node-pre-gyp` to `bundledDependencies`
  - Add `aws-sdk` as a `devDependency`
@@ -108,10 +107,10 @@ - Add a custom `install` script
     "dependencies"  : {
-      "node-pre-gyp": "0.6.x"
+      "node-pre-gyp": "0.5.x"
     },
+    "bundledDependencies":["node-pre-gyp"],
     "devDependencies": {
-      "aws-sdk": "2.x"
+      "aws-sdk": "~2.0.0-rc.15"
     }
     "scripts": {
-        "preinstall": "npm install node-pre-gyp",
-        "install": "node-pre-gyp install --fallback-to-build"
+        "install": "node-pre-gyp install --fallback-to-build",
     },
@@ -125,3 +124,3 @@ "binary": {
 
-For a full example see [node-addon-examples's package.json](https://github.com/springmeyer/node-addon-example/blob/master/package.json).
+For a full example see [node-addon-examples's package.json](https://github.com/springmeyer/node-addon-example/blob/2ff60a8ded7f042864ad21db00c3a5a06cf47075/package.json#L11-L22).
 
@@ -151,3 +150,3 @@ ##### The `binary` object has three required properties
   - Various node-pre-gyp commands like `publish` and `info` only work with an S3 host.
-  - S3 is a very solid hosting platform for distributing large files.
+  - S3 is a very solid hosting platform for distributing large files, even [Github recommends using it instead of github](https://help.github.com/articles/distributing-large-binaries).
   - We provide detail documentation for using [S3 hosting](#s3-hosting) with node-pre-gyp.
@@ -284,3 +283,3 @@
 
-You can host wherever you choose but S3 is cheap, `node-pre-gyp publish` expects it, and S3 can be integrated well with [Travis.ci](http://travis-ci.org) to automate builds for OS X and Ubuntu, and with [Appveyor](http://appveyor.com) to automate builds for Windows. Here is an approach to do this:
+You can host wherever you choose but S3 is cheap, `node-pre-gyp publish` expects it, and S3 can be integrated well with [travis.ci](http://travis-ci.org) to automate builds for OS X and Ubuntu. Here is an approach to do this:
 
@@ -404,3 +403,3 @@ First, get setup locally and test the workflow:
 
-NOTE: keys are per account but not per repo (this is difference than Travis where keys are per repo but not related to the account used to encrypt them).
+NOTE: keys are per account but not per repo (this is difference than travis where keys are per repo but not related to the account used to encrypt them).
 
@@ -413,3 +412,3 @@ #### 5) Hook up publishing
 
-You might wish to publish binaries only on a specific commit. To do this you could borrow from the [Travis.ci idea of commit keywords](http://about.travis-ci.org/docs/user/how-to-skip-a-build/) and add special handling for commit messages with `[publish binary]`:
+You might wish to publish binaries only on a specific commit. To do this you could borrow from the [travis.ci idea of commit keywords](http://about.travis-ci.org/docs/user/how-to-skip-a-build/) and add special handling for commit messages with `[publish binary]`:
 
@@ -423,4 +422,5 @@ SET CM=%APPVEYOR_REPO_COMMIT_MESSAGE%
 
-Remember this publishing is not the same as `npm publish`. We're just talking about the binary module here and not your entire npm package.
+Remember this publishing is not the same as `npm publish`. We're just talking about the binary module here and not your entire npm package. To automate the publishing of your entire package to npm on travis see http://about.travis-ci.org/docs/user/deployment/npm/
 
+
 ## Travis Automation
@@ -435,7 +435,7 @@
 
-Note: if you need 32 bit binaries, this can be done from a 64 bit Travis machine. See [the node-sqlite3 scripts for an example of doing this](https://github.com/mapbox/node-sqlite3/blob/bae122aa6a2b8a45f6b717fab24e207740e32b5d/scripts/build_against_node.sh#L54-L74).
+Note: if you need 32 bit binaries, this can be done from a 64 bit travis machine. See [the node-sqlite3 scripts for an example of doing this](https://github.com/mapbox/node-sqlite3/blob/bae122aa6a2b8a45f6b717fab24e207740e32b5d/scripts/build_against_node.sh#L54-L74).
 
 Below is a guide to getting set up:
 
-#### 1) Install the Travis gem
+#### 1) Install the travis gem
 
@@ -462,3 +462,3 @@ gem install travis
 
-More details on Travis encryption at http://about.travis-ci.org/docs/user/encryption-keys/.
+More details on travis encryption at http://about.travis-ci.org/docs/user/encryption-keys/.
 
@@ -541,5 +541,5 @@ #### 3) Hook up publishing
 
-You might wish to publish binaries only on a specific commit. To do this you could borrow from the [Travis.ci idea of commit keywords](http://about.travis-ci.org/docs/user/how-to-skip-a-build/) and add special handling for commit messages with `[publish binary]`:
+You might wish to publish binaries only on a specific commit. To do this you could borrow from the [travis.ci idea of commit keywords](http://about.travis-ci.org/docs/user/how-to-skip-a-build/) and add special handling for commit messages with `[publish binary]`:
 
-    COMMIT_MESSAGE=$(git log --format=%B --no-merges -n 1 | tr -d '\n')
+    COMMIT_MESSAGE=$(git show -s --format=%B $TRAVIS_COMMIT | tr -d '\n')
     if [[ ${COMMIT_MESSAGE} =~ "[publish binary]" ]]; then node-pre-gyp publish; fi;
@@ -555,6 +555,4 @@
 
-WARNING: if you are working in a pull request and publishing binaries from there then you will want to avoid double publishing when Travis.ci builds both the `push` and `pr`. You only want to run the publish on the `push` commit. See https://github.com/Project-OSRM/node-osrm/blob/8eb837abe2e2e30e595093d16e5354bc5c573575/scripts/is_pr_merge.sh which is called from https://github.com/Project-OSRM/node-osrm/blob/8eb837abe2e2e30e595093d16e5354bc5c573575/scripts/publish.sh for an example of how to do this.
+Remember this publishing is not the same as `npm publish`. We're just talking about the binary module here and not your entire npm package. To automate the publishing of your entire package to npm on travis see http://about.travis-ci.org/docs/user/deployment/npm/
 
-Remember this publishing is not the same as `npm publish`. We're just talking about the binary module here and not your entire npm package. To automate the publishing of your entire package to npm on Travis see http://about.travis-ci.org/docs/user/deployment/npm/
-
 # Versioning
@@ -561,0 +559,0 @@

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

Improved metrics

Lines of code

2511

increased by0.48%

Number of medium supply chain risk alerts

2

decreased by-33.33%

Worsened metrics

Total package byte prevSize

111261

decreased by-0.17%

Number of lines in readme file

571

decreased by-0.35%

No dependency changes