GitHub user zertosh opened a pull request:

    https://github.com/apache/thrift/pull/1175

    Update node library dependencies

    * The changes to node-int64 and Q are small:
      - https://github.com/broofa/node-int64/compare/v0.3.3...v0.4.0
      - https://github.com/kriskowal/q/compare/v1.0.1...v1.4.1
    * ws under went a rewrite between 0.4.32 and 2.0.1 
(https://github.com/websockets/ws/compare/0.4.32...2.0.1). The API as used by 
thrift is backwards compatible. However, ws now uses ES6 syntax, so it requires 
at least Node 4.
      - Most notable change here is that ws no longer tries to install binary 
modules.
    * Node 4 is now the minimally required version of Node, due to ws' 
requirement.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zertosh/thrift THRIFT-4064

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/thrift/pull/1175.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1175
    
----
commit face8c95163fc1b382ce7522b64334547fd43eca
Author: Andres Suarez <zert...@gmail.com>
Date:   2017-02-01T19:37:45Z

    Update node library dependencies
    
    * The changes to node-int64 and Q are small:
      - https://github.com/broofa/node-int64/compare/v0.3.3...v0.4.0
      - https://github.com/kriskowal/q/compare/v1.0.1...v1.4.1
    * ws under went a rewrite between 0.4.32 and 2.0.1 
(https://github.com/websockets/ws/compare/0.4.32...2.0.1). The API as used by 
thrift is backwards compatible. However, ws now uses ES6 syntax, so it requires 
at least Node 4.
      - Most notable change here is that ws no longer tries to install binary 
modules.
    * Node 4 is now the minimally required version of Node, due to ws' 
requirement.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to