<div dir="ltr">2015-09-24 14:42 GMT+02:00 Daniel Pocock <span dir="ltr"><<a href="mailto:daniel@pocock.pro" target="_blank">daniel@pocock.pro</a>></span>:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
This is failing because node-nan 2.x is now in unstable<br>
<br>
I've filed a bug upstream requesting support for node-nan 2.x<br></blockquote><div><br></div><div>This is the right thing to do.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Maybe both old and new versions of node-nan will be needed in stretch?<br></blockquote><div><br></div><div>This isn't ! The idea is to move forward to nodejs 4 / nan 2.</div><div>Maintaining legacy modules is more time-consuming than porting them</div><div>to nan 2.x - a task that i can do but that is best done by upstream.</div><div></div></div><br></div><div class="gmail_extra">Since the two files built using node-gyp and node-nan have been taken</div><div class="gmail_extra">from node-ws, and since node-ws has already been ported to node-nan 2,</div><div class="gmail_extra">i suggest to be patient...</div><div class="gmail_extra"><br></div><div class="gmail_extra">Jérémy.</div><div class="gmail_extra"><br></div></div>