fsevents 1.0.11 → 1.0.17

package/node_modules/minimist/package.json

@@ -1,26 +1,34 @@
 {
   "_args": [
     [
-      "minimist@0.0.8",
+      {
+        "raw": "minimist@0.0.8",
+        "scope": null,
+        "escapedName": "minimist",
+        "name": "minimist",
+        "rawSpec": "0.0.8",
+        "spec": "0.0.8",
+        "type": "version"
+      },
       "/Users/eshanker/Code/fsevents/node_modules/mkdirp"
     ]
   ],
   "_from": "minimist@0.0.8",
   "_id": "minimist@0.0.8",
   "_inCache": true,
-  "_installable": true,
   "_location": "/minimist",
   "_npmUser": {
-    "email": "mail@substack.net",
-    "name": "substack"
+    "name": "substack",
+    "email": "mail@substack.net"
   },
   "_npmVersion": "1.4.3",
   "_phantomChildren": {},
   "_requested": {
-    "name": "minimist",
     "raw": "minimist@0.0.8",
-    "rawSpec": "0.0.8",
     "scope": null,
+    "escapedName": "minimist",
+    "name": "minimist",
+    "rawSpec": "0.0.8",
     "spec": "0.0.8",
     "type": "version"
   },
@@ -33,8 +41,8 @@
   "_spec": "minimist@0.0.8",
   "_where": "/Users/eshanker/Code/fsevents/node_modules/mkdirp",
   "author": {
-    "email": "mail@substack.net",
     "name": "James Halliday",
+    "email": "mail@substack.net",
     "url": "http://substack.net"
   },
   "bugs": {
@@ -55,8 +63,8 @@
   "keywords": [
     "argv",
     "getopt",
-    "optimist",
-    "parser"
+    "parser",
+    "optimist"
   ],
   "license": "MIT",
   "main": "index.js",
@@ -77,17 +85,17 @@
     "test": "tap test/*.js"
   },
   "testling": {
+    "files": "test/*.js",
     "browsers": [
-      "chrome/10",
-      "chrome/latest",
+      "ie/6..latest",
       "ff/5",
       "firefox/latest",
-      "ie/6..latest",
-      "opera/12",
+      "chrome/10",
+      "chrome/latest",
       "safari/5.1",
-      "safari/latest"
-    ],
-    "files": "test/*.js"
+      "safari/latest",
+      "opera/12"
+    ]
   },
   "version": "0.0.8"
 }

package/node_modules/mkdirp/package.json

@@ -1,41 +1,51 @@
 {
   "_args": [
     [
-      "mkdirp@~0.3 || 0.4 || 0.5",
-      "/Users/eshanker/Code/fsevents/node_modules/tap"
+      {
+        "raw": "mkdirp@~0.5.1",
+        "scope": null,
+        "escapedName": "mkdirp",
+        "name": "mkdirp",
+        "rawSpec": "~0.5.1",
+        "spec": ">=0.5.1 <0.6.0",
+        "type": "range"
+      },
+      "/Users/eshanker/Code/fsevents/node_modules/node-pre-gyp"
     ]
   ],
-  "_from": "mkdirp@>=0.3.0 <0.4.0||>=0.4.0 <0.5.0||>=0.5.0 <0.6.0",
+  "_from": "mkdirp@>=0.5.1 <0.6.0",
   "_id": "mkdirp@0.5.1",
   "_inCache": true,
-  "_installable": true,
   "_location": "/mkdirp",
   "_nodeVersion": "2.0.0",
   "_npmUser": {
-    "email": "substack@gmail.com",
-    "name": "substack"
+    "name": "substack",
+    "email": "substack@gmail.com"
   },
   "_npmVersion": "2.9.0",
   "_phantomChildren": {},
   "_requested": {
-    "name": "mkdirp",
-    "raw": "mkdirp@~0.3 || 0.4 || 0.5",
-    "rawSpec": "~0.3 || 0.4 || 0.5",
+    "raw": "mkdirp@~0.5.1",
     "scope": null,
-    "spec": ">=0.3.0 <0.4.0||>=0.4.0 <0.5.0||>=0.5.0 <0.6.0",
+    "escapedName": "mkdirp",
+    "name": "mkdirp",
+    "rawSpec": "~0.5.1",
+    "spec": ">=0.5.1 <0.6.0",
     "type": "range"
   },
   "_requiredBy": [
+    "/fstream",
+    "/node-pre-gyp",
     "/tap"
   ],
   "_resolved": "https://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz",
   "_shasum": "30057438eac6cf7f8c4767f38648d6697d75c903",
   "_shrinkwrap": null,
-  "_spec": "mkdirp@~0.3 || 0.4 || 0.5",
-  "_where": "/Users/eshanker/Code/fsevents/node_modules/tap",
+  "_spec": "mkdirp@~0.5.1",
+  "_where": "/Users/eshanker/Code/fsevents/node_modules/node-pre-gyp",
   "author": {
-    "email": "mail@substack.net",
     "name": "James Halliday",
+    "email": "mail@substack.net",
     "url": "http://substack.net"
   },
   "bin": {
@@ -60,8 +70,8 @@
   "gitHead": "d4eff0f06093aed4f387e88e9fc301cb76beedc7",
   "homepage": "https://github.com/substack/node-mkdirp#readme",
   "keywords": [
-    "directory",
-    "mkdir"
+    "mkdir",
+    "directory"
   ],
   "license": "MIT",
   "main": "index.js",

package/node_modules/ms/History.md

@@ -0,0 +1,66 @@
+
+0.7.1 / 2015-04-20
+==================
+
+  * prevent extraordinary long inputs (@evilpacket)
+  * Fixed broken readme link
+
+0.7.0 / 2014-11-24
+==================
+
+ * add time abbreviations, updated tests and readme for the new units
+ * fix example in the readme.
+ * add LICENSE file
+
+0.6.2 / 2013-12-05
+==================
+
+ * Adding repository section to package.json to suppress warning from NPM.
+
+0.6.1 / 2013-05-10
+==================
+
+  * fix singularization [visionmedia]
+
+0.6.0 / 2013-03-15
+==================
+
+  * fix minutes
+
+0.5.1 / 2013-02-24
+==================
+
+  * add component namespace
+
+0.5.0 / 2012-11-09
+==================
+
+  * add short formatting as default and .long option
+  * add .license property to component.json
+  * add version to component.json
+
+0.4.0 / 2012-10-22
+==================
+
+  * add rounding to fix crazy decimals
+
+0.3.0 / 2012-09-07
+==================
+
+  * fix `ms(<String>)` [visionmedia]
+
+0.2.0 / 2012-09-03
+==================
+
+  * add component.json [visionmedia]
+  * add days support [visionmedia]
+  * add hours support [visionmedia]
+  * add minutes support [visionmedia]
+  * add seconds support [visionmedia]
+  * add ms string support [visionmedia]
+  * refactor tests to facilitate ms(number) [visionmedia]
+
+0.1.0 / 2012-03-07
+==================
+
+  * Initial release

package/node_modules/ms/package.json

@@ -1,20 +1,46 @@
 {
+  "_args": [
+    [
+      {
+        "raw": "ms@0.7.1",
+        "scope": null,
+        "escapedName": "ms",
+        "name": "ms",
+        "rawSpec": "0.7.1",
+        "spec": "0.7.1",
+        "type": "version"
+      },
+      "/Users/eshanker/Code/fsevents/node_modules/debug"
+    ]
+  ],
   "_from": "ms@0.7.1",
   "_id": "ms@0.7.1",
+  "_inCache": true,
   "_location": "/ms",
   "_nodeVersion": "0.12.2",
   "_npmUser": {
-    "email": "rauchg@gmail.com",
-    "name": "rauchg"
+    "name": "rauchg",
+    "email": "rauchg@gmail.com"
   },
   "_npmVersion": "2.7.5",
   "_phantomChildren": {},
+  "_requested": {
+    "raw": "ms@0.7.1",
+    "scope": null,
+    "escapedName": "ms",
+    "name": "ms",
+    "rawSpec": "0.7.1",
+    "spec": "0.7.1",
+    "type": "version"
+  },
   "_requiredBy": [
     "/debug"
   ],
   "_resolved": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz",
   "_shasum": "9cd13c03adbff25b65effde7ce864ee952017098",
   "_shrinkwrap": null,
+  "_spec": "ms@0.7.1",
+  "_where": "/Users/eshanker/Code/fsevents/node_modules/debug",
   "bugs": {
     "url": "https://github.com/guille/ms.js/issues"
   },
@@ -33,7 +59,7 @@
   "directories": {},
   "dist": {
     "shasum": "9cd13c03adbff25b65effde7ce864ee952017098",
-    "tarball": "http://registry.npmjs.org/ms/-/ms-0.7.1.tgz"
+    "tarball": "https://registry.npmjs.org/ms/-/ms-0.7.1.tgz"
   },
   "gitHead": "713dcf26d9e6fd9dbc95affe7eff9783b7f1b909",
   "homepage": "https://github.com/guille/ms.js",

package/node_modules/node-pre-gyp/CHANGELOG.md

@@ -1,8 +1,45 @@
 # node-pre-gyp changelog
 
+## 0.6.32
+
+ - Honor npm configuration for CA bundles (@heikkipora)
+ - Add node-pre-gyp and npm versions to user agent (@addaleax)
+ - Updated various deps
+ - Add known node version for v7.x
+
+## 0.6.31
+
+ - Updated various deps
+
+## 0.6.30
+
+ - Update to npmlog@4.x and semver@5.3.x
+ - Add known node version for v6.5.0
+
+## 0.6.29
+
+ - Add known node versions for v0.10.45, v0.12.14, v4.4.4, v5.11.1, and v6.1.0
+
+## 0.6.28
+
+ - Now more verbose when remote binaries are not available. This is needed since npm is increasingly more quiet by default
+   and users need to know why builds are falling back to source compiles that might then error out.
+
+## 0.6.27
+
+ - Add known node version for node v6
+ - Stopped bundling dependencies
+ - Documented method for module authors to avoid bundling node-pre-gyp
+   - See https://github.com/mapbox/node-pre-gyp/tree/master#configuring for details
+
+## 0.6.26
+
+ - Skip validation for nw runtime (https://github.com/mapbox/node-pre-gyp/pull/181) via @fleg
+
 ## 0.6.25
 
  - Improved support for auto-detection of electron runtime in `node-pre-gyp.find()`
+   - Pull request from @enlight - https://github.com/mapbox/node-pre-gyp/pull/187
  - Add known node version for 4.4.1 and 5.9.1
 
 ## 0.6.24

package/node_modules/node-pre-gyp/README.md

@@ -12,9 +12,9 @@
 
 ### Features
 
- - 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.
- - A Javascript module that can dynamically require your installed binary: `require('node-pre-gyp').find`
+ - A JavaScript module that can dynamically require your installed binary: `require('node-pre-gyp').find`
 
 For a hello world example of a module packaged with `node-pre-gyp` see <https://github.com/springmeyer/node-addon-example> and [the wiki ](https://github.com/mapbox/node-pre-gyp/wiki/Modules-using-node-pre-gyp) for real world examples.
 
@@ -30,7 +30,7 @@ See the [Frequently Ask Questions](https://github.com/mapbox/node-pre-gyp/wiki/F
 
 ## Depends
 
- - Node.js 0.12.x -> 0.8.x
+ - Node.js >= node v0.10.x
 
 ## Install
 
@@ -71,6 +71,7 @@ Options include:
 
  - `-C/--directory`: run the command in this directory
  - `--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
  - `--fallback-to-build`: fallback to building from source if pre-built binary is not available
  - `--target=0.10.25`: Pass the target node or node-webkit version to compile against
@@ -91,7 +92,7 @@ This is a guide to configuring your module to use node-pre-gyp.
 
 #### 1) Add new entries to your `package.json`
 
- - Add `node-pre-gyp` to `bundledDependencies`
+ - Add `node-pre-gyp` to `dependencies`
  - Add `aws-sdk` as a `devDependency`
  - Add a custom `install` script
  - Declare a `binary` object
@@ -100,14 +101,14 @@ This looks like:
 
 ```js
     "dependencies"  : {
-      "node-pre-gyp": "0.5.x"
+      "node-pre-gyp": "0.6.x"
     },
-    "bundledDependencies":["node-pre-gyp"],
     "devDependencies": {
-      "aws-sdk": "~2.0.0-rc.15"
+      "aws-sdk": "2.x"
     }
     "scripts": {
-        "install": "node-pre-gyp install --fallback-to-build",
+        "preinstall": "npm install node-pre-gyp",
+        "install": "node-pre-gyp install --fallback-to-build"
     },
     "binary": {
         "module_name": "your_module",
@@ -116,7 +117,7 @@ This looks like:
     }
 ```
 
-For a full example see [node-addon-examples's package.json](https://github.com/springmeyer/node-addon-example/blob/2ff60a8ded7f042864ad21db00c3a5a06cf47075/package.json#L11-L22).
+For a full example see [node-addon-examples's package.json](https://github.com/springmeyer/node-addon-example/blob/master/package.json).
 
 ##### The `binary` object has three required properties
 
@@ -141,10 +142,12 @@ A url to the remote location where you've published tarball binaries (must be `h
 It is highly recommended that you use Amazon S3. The reasons are:
 
   - 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, even [Github recommends using it instead of github](https://help.github.com/articles/distributing-large-binaries).
+  - S3 is a very solid hosting platform for distributing large files.
   - We provide detail documentation for using [S3 hosting](#s3-hosting) with node-pre-gyp.
 
-Why then not require S3? Because while some applications using node-pre-gyp need to distribute binaries as large as 20-30 MB, others might have very small binaries and might wish to store them in a github repo. This is not recommended, but if an author really wants to host in a non-s3 location then it should be possible.
+Why then not require S3? Because while some applications using node-pre-gyp need to distribute binaries as large as 20-30 MB, others might have very small binaries and might wish to store them in a GitHub repo. This is not recommended, but if an author really wants to host in a non-s3 location then it should be possible.
+
+It should also be mentioned that there is an optional and entirely separate npm module called [node-pre-gyp-github](https://github.com/bchr02/node-pre-gyp-github) which is intended to complement node-pre-gyp and be installed along with it. It provides the ability to store and publish your binaries within your repositories GitHub Releases if you would rather not use S3 directly. Installation and usage instructions can be found [here](https://github.com/bchr02/node-pre-gyp-github), but the basic premise is that instead of using the ```node-pre-gyp publish``` command you would use ```node-pre-gyp-github publish```.
 
 ##### The `binary` object has two optional properties
 
@@ -273,7 +276,7 @@ If a a binary was not available for a given platform and `--fallback-to-build` w
 
 ## S3 Hosting
 
-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:
+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:
 
 First, get setup locally and test the workflow:
 
@@ -368,15 +371,15 @@ Below is a guide to getting set up:
 
 #### 1) Create a free Appveyor account
 
-Go to https://ci.appveyor.com/signup/free and sign in with your github account.
+Go to https://ci.appveyor.com/signup/free and sign in with your GitHub account.
 
 #### 2) Create a new project
 
-Go to https://ci.appveyor.com/projects/new and select the github repo for your module
+Go to https://ci.appveyor.com/projects/new and select the GitHub repo for your module
 
 #### 3) Add appveyor.yml and push it
 
-Once you have committed an `appveyor.yml` ([appveyor.yml reference](http://www.appveyor.com/docs/appveyor-yml)) to your github repo and pushed it appveyor should automatically start building your project.
+Once you have committed an `appveyor.yml` ([appveyor.yml reference](http://www.appveyor.com/docs/appveyor-yml)) to your GitHub repo and pushed it AppVeyor should automatically start building your project.
 
 #### 4) Create secure variables
 
@@ -392,7 +395,7 @@ environment:
     secure: W1rwNoSnOku1r+28gnoufO8UA8iWADmL1LiiwH9IOkIVhDTNGdGPJqAlLjNqwLnL
 ```
 
-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).
 
 #### 5) Hook up publishing
 
@@ -400,7 +403,7 @@ Just put `node-pre-gyp package publish` in your `appveyor.yml` after `npm instal
 
 #### 6) Publish when you want
 
-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]`:
 
     SET CM=%APPVEYOR_REPO_COMMIT_MESSAGE%
     if not "%CM%" == "%CM:[publish binary]=%" node-pre-gyp --msvs_version=2013 publish
@@ -409,8 +412,7 @@ If your commit message contains special characters (e.g. `&`) this method might
 
     ps: if($env:APPVEYOR_REPO_COMMIT_MESSAGE.ToLower().Contains('[publish binary]')) { node-pre-gyp --msvs_version=2013 publish }
 
-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.
 
 ## Travis Automation
 
@@ -421,11 +423,11 @@ Remember this publishing is not the same as `npm publish`. We're just talking ab
 
 For an example of doing this see [node-add-example's .travis.yml](https://github.com/springmeyer/node-addon-example/blob/2ff60a8ded7f042864ad21db00c3a5a06cf47075/.travis.yml).
 
-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
 
     gem install travis
 
@@ -447,7 +449,7 @@ env:
     - secure: o2nkUQIiABD139XS6L8pxq3XO5gch27hvm/gOdV+dzNKc/s2KomVPWcOyXNxtJGhtecAkABzaW8KHDDi5QL1kNEFx6BxFVMLO8rjFPsMVaBG9Ks6JiDQkkmrGNcnVdxI/6EKTLHTH5WLsz8+J7caDBzvKbEfTux5EamEhxIWgrI=
 ```
 
-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/.
 
 #### 3) Hook up publishing
 
@@ -455,7 +457,7 @@ Just put `node-pre-gyp package publish` in your `.travis.yml` after `npm install
 
 ##### OS X publishing
 
-If you want binaries for OS X in addition to linux you can enable [multi-os for travis](http://docs.travis-ci.com/user/multi-os/#Setting-.travis.yml)
+If you want binaries for OS X in addition to linux you can enable [multi-os for Travis](http://docs.travis-ci.com/user/multi-os/#Setting-.travis.yml)
 
 Use a configuration like:
 
@@ -479,7 +481,7 @@ before_install:
 - nvm use $NODE_VERSION
 ```
 
-See [Travis OS X Gochas](#travis-os-x-gochas) for why we replace `language: node_js` and `node_js:` sections with `language: cpp` and a custom matrix.
+See [Travis OS X Gotchas](#travis-os-x-gotchas) for why we replace `language: node_js` and `node_js:` sections with `language: cpp` and a custom matrix.
 
 Also create platform specific sections for any deps that need install. For example if you need libpng:
 
@@ -490,15 +492,15 @@ Also create platform specific sections for any deps that need install. For examp
 
 For detailed multi-OS examples see [node-mapnik](https://github.com/mapnik/node-mapnik/blob/master/.travis.yml) and [node-sqlite3](https://github.com/mapbox/node-sqlite3/blob/master/.travis.yml).
 
-##### Travis OS X Gochas
+##### Travis OS X Gotchas
 
-First, unlike the Travis linux machines the OS X machines do not put `node-pre-gyp` on PATH by default. So to you will need to:
+First, unlike the Travis Linux machines, the OS X machines do not put `node-pre-gyp` on PATH by default. To do so you will need to:
 
 ```sh
 export PATH=$(pwd)/node_modules/.bin:${PATH}
 ```
 
-Second, the OS X machines doe not support using a matrix for installing node.js different versions. So you need to bootstrap the installation of node.js in a cross platform way.
+Second, the OS X machines do not support using a matrix for installing different Node.js versions. So you need to bootstrap the installation of Node.js in a cross platform way.
 
 By doing:
 
@@ -525,9 +527,9 @@ node_js:
 
 #### 4) Publish when you want
 
-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 show -s --format=%B $TRAVIS_COMMIT | tr -d '\n')
+    COMMIT_MESSAGE=$(git log --format=%B --no-merges -n 1 | tr -d '\n')
     if [[ ${COMMIT_MESSAGE} =~ "[publish binary]" ]]; then node-pre-gyp publish; fi;
 
 Then you can trigger new binaries to be built like:
@@ -538,7 +540,9 @@ Or, if you don't have any changes to make simply run:
 
     git commit --allow-empty -m "[publish binary]"
 
-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/
+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/
 
 # Versioning
 

package/node_modules/node-pre-gyp/appveyor.yml

@@ -1,8 +1,14 @@
+os: Visual Studio 2015
+
 environment:
+  AWS_ACCESS_KEY_ID:
+    secure: "VVcArESQA6N2JeG/SkeMYVnHn5DMEuiwbsKHez3fzuA="
+  AWS_SECRET_ACCESS_KEY:
+    secure: "7lqDDrORt+VRTfVZh1ZcK5P3bAhFuiND9WmbDedehxLoqqdSiy8SBKWuKE2qVKyI"
   matrix:
-    - nodejs_version: 0.10.36
-    - nodejs_version: 0.12.0
-    - nodejs_version: 1.2.0
+    - nodejs_version: 0.10
+    - nodejs_version: 4
+    - nodejs_version: 6
 
 platform:
   - x64
@@ -12,18 +18,22 @@ shallow_clone: true
 
 install:
   - ps: Install-Product node $env:nodejs_version $env:Platform
+  - ps: Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
+  - npm install --global --production npm-windows-upgrade
+  # https://github.com/nodejs/node-gyp/issues/972#issuecomment-231055109
+  - npm-windows-upgrade --npm-version 2.15.9 --no-dns-check --no-prompt
   - node --version
   - npm --version
-  - SET PATH=%APPDATA%\npm;%PATH%
-  - npm update -g npm
-  - npm --version
+  #- SET PATH=%APPDATA%\npm;%PATH%
+  #- npm install -g node-gyp
+  - npm install -g node-gyp@3.2.1
   - node -e "console.log(process.arch);"
-  - SET PATH=C:\Program Files (x86)\MSBuild\12.0\bin\;%PATH%
-  - if "%PLATFORM%" == "x64" set PATH=C:\Python27-x64;%PATH%
-  - if "%PLATFORM%" == "x86" SET PATH=C:\python27;%PATH%
+  - IF /I "%PLATFORM%" == "x64" set PATH=C:\Python27-x64;%PATH%
+  - IF /I "%PLATFORM%" == "x86" SET PATH=C:\python27;%PATH%
+  - IF /I "%PLATFORM%" == "x64" CALL "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64
+  - IF /I "%PLATFORM%" == "x86" CALL "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x86
   - npm install
   - npm test
-  - .\scripts\test.bat
 
 build: off
 test: off