node-pre-gyp - npm Package Compare versions

Comparing version 0.9.1 to 0.10.0

CHANGELOG.md

 # node-pre-gyp changelog
 
+## 0.10.0
+
+- Allow for a single-level module path when packing @allenluce (https://github.com/mapbox/node-pre-gyp/pull/371)
+- Log warnings instead of errors when falling back @xzyfer (https://github.com/mapbox/node-pre-gyp/pull/366)
+- Add Node.js v10 support to tests (https://github.com/mapbox/node-pre-gyp/pull/372)
+- Remove retire.js from CI (https://github.com/mapbox/node-pre-gyp/pull/372)
+- Remove support for Node.js v4 due to [EOL on April 30th, 2018](https://github.com/nodejs/Release/blob/7dd52354049cae99eed0e9fe01345b0722a86fde/schedule.json#L14)
+- Update appveyor tests to install default NPM version instead of NPM v2.x for all Windows builds (https://github.com/mapbox/node-pre-gyp/pull/375)
+
 ## 0.9.1
@@ -245,3 +254,3 @@
 
- - Fixed support for auto-detecting s3 bucket name when it contains `.` - @taavo 
+ - Fixed support for auto-detecting s3 bucket name when it contains `.` - @taavo
  - Fixed support for installing when path contains a `'` - @halfdan
@@ -381,3 +390,3 @@ - Ported tests to mocha
 
- - Fixed exception when only stderr is available in binary test (@bendi / #31) 
+ - Fixed exception when only stderr is available in binary test (@bendi / #31)
 
@@ -403,2 +412,1 @@ ## 0.4.0
  - `.node` modules must be in a folder of there own since tar-pack will remove everything when it unpacks.
-

contributing.md

@@ -6,6 +6,6 @@ # Contributing
 
-- Ensure tests are passing on travis (okay for appveyor node v4 x86 to fail)
+- Ensure tests are passing on travis and appveyor
 - Run `node scripts/abi_crosswalk.js` and commit any changes
 - Update the changelog
 - Tag a new release like: `git tag -a v0.6.34 -m "tagging v0.6.34" && git push --tags`
-- Run `npm publish`
+- Run `npm publish`

lib/install.js

@@ -145,4 +145,4 @@ "use strict";
         full_message += fallback_message;
-        log.error("Tried to download(" + err.statusCode + "): " + opts.hosted_tarball);
-        log.error(full_message);
+        log.warn("Tried to download(" + err.statusCode + "): " + opts.hosted_tarball);
+        log.warn(full_message);
         log.http(err.message);
@@ -155,4 +155,4 @@ } else {
         full_message += fallback_message;
-        log.error(full_message);
-        log.error("Hit error " + err.message);
+        log.warn(full_message);
+        log.warn("Hit error " + err.message);
     }
@@ -159,0 +159,0 @@ }

lib/package.js

@@ -36,5 +36,8 @@ "use strict";
         mkdirp(path.dirname(tarball),function(err) {
-            from = path.dirname(from);
             if (err) return callback(err);
             packlist({ path: from }).then(function(files) {
+                var base = path.basename(from);
+                files = files.map(function(file) {
+                    return path.join(base, file);
+                });
                 tar.create({
@@ -45,3 +48,3 @@ portable: true,
                     file: tarball,
-                    cwd: from
+                    cwd: path.dirname(from)
                 }, files, function(err) {
@@ -48,0 +51,0 @@ if (err)  console.error('['+package_json.name+'] ' + err.message);

lib/util/abi_crosswalk.json

@@ -1266,2 +1266,10 @@ {
   },
+  "4.9.0": {
+    "node_abi": 46,
+    "v8": "4.5"
+  },
+  "4.9.1": {
+    "node_abi": 46,
+    "v8": "4.5"
+  },
   "5.0.0": {
@@ -1483,2 +1491,14 @@ "node_abi": 47,
   },
+  "6.14.0": {
+    "node_abi": 48,
+    "v8": "5.1"
+  },
+  "6.14.1": {
+    "node_abi": 48,
+    "v8": "5.1"
+  },
+  "6.14.2": {
+    "node_abi": 48,
+    "v8": "5.1"
+  },
   "7.0.0": {
@@ -1636,2 +1656,10 @@ "node_abi": 51,
   },
+  "8.11.0": {
+    "node_abi": 57,
+    "v8": "6.2"
+  },
+  "8.11.1": {
+    "node_abi": 57,
+    "v8": "6.2"
+  },
   "9.0.0": {
@@ -1684,3 +1712,27 @@ "node_abi": 59,
     "v8": "6.2"
+  },
+  "9.9.0": {
+    "node_abi": 59,
+    "v8": "6.2"
+  },
+  "9.10.0": {
+    "node_abi": 59,
+    "v8": "6.2"
+  },
+  "9.10.1": {
+    "node_abi": 59,
+    "v8": "6.2"
+  },
+  "9.11.0": {
+    "node_abi": 59,
+    "v8": "6.2"
+  },
+  "9.11.1": {
+    "node_abi": 59,
+    "v8": "6.2"
+  },
+  "10.0.0": {
+    "node_abi": 64,
+    "v8": "6.6"
   }
 }

package.json

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

README.md

@@ -33,3 +33,3 @@ # node-pre-gyp
 
- - Node.js >= node v4.x
+ - Node.js >= node v6.x
 
@@ -291,7 +291,7 @@ ## Install
 
-[N-API](https://nodejs.org/api/n-api.html#n_api_n_api) is an ABI-stable alternative to previous technologies such as [nan](https://github.com/nodejs/nan) which are tied to a specific Node runtime engine. N-API is Node runtime engine agnostic and guarantees modules created today will continue to run, without changes, into the future. 
+[N-API](https://nodejs.org/api/n-api.html#n_api_n_api) is an ABI-stable alternative to previous technologies such as [nan](https://github.com/nodejs/nan) which are tied to a specific Node runtime engine. N-API is Node runtime engine agnostic and guarantees modules created today will continue to run, without changes, into the future.
 
-Using `node-pre-gyp` with N-API projects requires a handful of additional configuration values and imposes some additional requirements. 
+Using `node-pre-gyp` with N-API projects requires a handful of additional configuration values and imposes some additional requirements.
 
-The most significant difference is that an N-API module can be coded to target multiple  N-API versions. Therefore, an N-API module must declare in its `package.json` file which N-API versions the module is designed to run against. In addition, since multiple builds may be required for a single module, path and file names must be specified in way that avoids naming conflicts. 
+The most significant difference is that an N-API module can be coded to target multiple  N-API versions. Therefore, an N-API module must declare in its `package.json` file which N-API versions the module is designed to run against. In addition, since multiple builds may be required for a single module, path and file names must be specified in way that avoids naming conflicts.
 
@@ -313,7 +313,7 @@ ### The `napi_versions` array property
 
-When the `napi_versions` array property is present, `node-pre-gyp` fires off multiple operations, one for each of the N-API versions in the array. In the example above, two operations are initiated, one for N-API version 1 and second for N-API version 3. How this version number is communicated is described next. 
+When the `napi_versions` array property is present, `node-pre-gyp` fires off multiple operations, one for each of the N-API versions in the array. In the example above, two operations are initiated, one for N-API version 1 and second for N-API version 3. How this version number is communicated is described next.
 
 ### The `napi_build_version` value
 
-For each of the N-API module operations `node-pre-gyp` initiates, it insures that the `napi_build_version` is set appropriately. 
+For each of the N-API module operations `node-pre-gyp` initiates, it insures that the `napi_build_version` is set appropriately.
 
@@ -323,3 +323,3 @@ This value is of importance in two areas:
 1. The C/C++ code which needs to know against which N-API version it should compile.
-2. `node-pre-gyp` itself which must assign appropriate path and file names to avoid collisions. 
+2. `node-pre-gyp` itself which must assign appropriate path and file names to avoid collisions.
 
@@ -340,3 +340,3 @@ ### Defining `NAPI_BUILD_VERSION` for the C/C++ code
 
-Since `node-pre-gyp` fires off multiple operations for each request, it is essential that path and file names be created in such a way as to avoid collisions. This is accomplished by imposing additional path and file naming requirements. 
+Since `node-pre-gyp` fires off multiple operations for each request, it is essential that path and file names be created in such a way as to avoid collisions. This is accomplished by imposing additional path and file naming requirements.
 
@@ -360,9 +360,9 @@ Specifically, when performing N-API builds, the `{napi_build_version}` text substitution string  *must* be present in the `module_path` property. In addition, the `{napi_build_version}` text substitution string  *must* be present in either the `remote_path` or `package_name` property. (No problem if it's in both.)
 
-For those who need them in legacy projects, two additional configuration values are available for all builds. 
+For those who need them in legacy projects, two additional configuration values are available for all builds.
 
-1. `napi_version` If N-API is supported by the currently executing Node instance, this value is the N-API version number supported by Node. If N-API is not supported, this value is an empty string. 
+1. `napi_version` If N-API is supported by the currently executing Node instance, this value is the N-API version number supported by Node. If N-API is not supported, this value is an empty string.
 
 2. `node_abi_napi` If the value returned for `napi_version` is non empty, this value is `'napi'`. If the value returned for `napi_version` is empty, this value is the value returned for `node_abi`.
 
-These values are present for use in the `binding.gyp` file and may be used as `{napi_version}` and `{node_abi_napi}` for text substituion in the `binary` properties of the `package.json` file. 
+These values are present for use in the `binding.gyp` file and may be used as `{napi_version}` and `{node_abi_napi}` for text substituion in the `binary` properties of the `package.json` file.
 
@@ -369,0 +369,0 @@ ## S3 Hosting

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

New author

Supply chain risk

A 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

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

Improved metrics

Total package byte prevSize

140038

increased by0.84%

Lines of code

3270

increased by1.71%

Worsened metrics

Number of medium supply chain risk alerts

3

increased by50%

No dependency changes