[Pkg-javascript-devel] Is it worth packaging node-setimmediate or not?

[Jérémy Lal]

Le dimanche 24 août 2014 à 22:08 +0100, Tim Retout a écrit :
> Hi,
> 
> Pump.io depends on set-immediate [0], which is deprecated in favour of
> setimmediate [1]:
> 
> [0] https://github.com/jussi-kalliokoski/setImmediate.js
> [1] https://github.com/YuzuJS/setImmediate

You should tell upstream pump.io to switch to the not deprecated lib.


> However, I've noticed that Debian only has nodejs >= 0.10, and so I
> believe require("setimmediate") is always a no-op (under node).

Yes, setImmediate is a global function.


> It occurs to me that the polyfill might be useful in browsers, so it's
> probably worth packaging as libjs-setimmediate, but I don't need it
> for that right now.

It boils down to "do browserify use it ?" ?


> Quite a few npm packages seem to depend on setimmediate, so is it
> worth packaging just so that the dependencies can be fulfilled?  Or is
> it better to patch out the calls to require("setimmediate") in the
> dependent packages?

That's what we're doing for
require('readable-stream')

In fact it'd avoid us patches to provide some modules in a bundle we are
talking about on pkg-javascript.

Jérémy.