[Pkg-javascript-devel] Bug#799656: NaN 2.x issue

[Daniel Pocock]

On 24/09/15 15:16, Jérémy Lal wrote:
> 
> 
> 2015-09-24 14:59 GMT+02:00 Daniel Pocock <daniel at pocock.pro
> <mailto:daniel at pocock.pro>>:
> 
> 
> 
>     On 24/09/15 14:53, Jérémy Lal wrote:
>     > 2015-09-24 14:42 GMT+02:00 Daniel Pocock <daniel at pocock.pro <mailto:daniel at pocock.pro>
>     > <mailto:daniel at pocock.pro <mailto:daniel at pocock.pro>>>:
>     >
>     >
>     >
>     >     This is failing because node-nan 2.x is now in unstable
>     >
>     >     I've filed a bug upstream requesting support for node-nan 2.x
>     >
>     >
>     > This is the right thing to do.
>     >
>     >
>     >     Maybe both old and new versions of node-nan will be needed in stretch?
>     >
>     >
>     > This isn't ! The idea is to move forward to nodejs 4 / nan 2.
>     > Maintaining legacy modules is more time-consuming than porting them
>     > to nan 2.x - a task that i can do but that is best done by upstream.
>     >
>     > Since the two files built using node-gyp and node-nan have been taken
>     > from node-ws, and since node-ws has already been ported to node-nan 2,
>     > i suggest to be patient...
>     >
> 
> 
>     I saw comments in another bug tracker suggesting that some upstreams are
>     not rushing into node-nan 2 as it is not a trivial change for them.
> 
>     I only reported this upstream today, so let's see how they respond.
> 
> 
> 
> Being an upstream node-nan user too, i can say that while it's not
> completely trivial,
> it's usually quickly done and depends linearly on the size of the project.
> For the files in node-websocket, it IS trivial since they are copies of
> projects that already
> moved to nan 2. Expect a quick response :)
> 

Will you be putting node-nan 2 into jessie-backports as well?  Or will I
need to keep a legacy version of node-websocket there?