Le mar. 1 janv. 2019 à 19:41, Mattia Rizzolo <[email protected]> a écrit :
> On Tue, Jan 01, 2019 at 06:48:00PM +0100, Jérémy Lal wrote:
> > > No the problem is that I have at least 20 package in my ddpo to fix
> >
> > Would there be a way for nodejs to know it's running in a test
> environment
> > and not print deprecation warnings there ?
> > If so we should tell it to nodejs maintainer :)
>
> That sounds like an odd thought to me: one would usually *want*
> deprecation warnings in testing enviroments, exactly so they can
> automatically catch such deprecation before it's too late and need to
> rush on them.
>
>
> I don't know this particular error, but if Jeremy claims it's easy to
> fix, surely fixing 20odds is doable?
> Hiding or ignoring all deprecation warnings sounds not really
> future-proof.
>
Yes it ils preferable but it will block transition to testing.
Better between release will be to revert to behavior of node v8 maybe.
Or mass fix by using Buffer = require('safe-buffer').Buffer
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
> more about me: https://mapreri.org : :' :
> Launchpad user: https://launchpad.net/~mapreri `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
> --
> Pkg-javascript-devel mailing list
> [email protected]
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
--
Pkg-javascript-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
