DeprecationWarning: Using Buffer without `new` will soon stop working

[amaramth]

0x prints this error message: (node:49959) DeprecationWarning: Using Buffer without new will soon stop working. Use new Buffer(), or preferably Buffer.from(), Buffer.allocUnsafe() or Buffer.alloc() instead.

[davidmarkclements]

thanks @alice0meta - we'll get round to this, (providing it's not a sub-dep that hasn't also updated yet, in which case we'll update subdep when it's resolved the deprecation notice)

0x will still work fine for now - fwiy deprecating Buffer without new was a terrible idea that's going to affect a lot of people unnecessarily

[yoshuawuyts]

chances are big this'll be reverted as breakage throughout npm is severe
and it can easily be resolved in other ways

On Wed, Nov 23, 2016 at 3:20 PM David Mark Clements <
notifications@github.com> wrote:

thanks @alice0meta https://github.com/alice0meta - we'll get round to
this, (providing it's not a sub-dep that hasn't also updated yet, in which
case we'll update subdep when it's resolved the deprecation notice)

0x will still work fine for now - fwiy deprecating Buffer without new was
a terrible idea that's going to affect a lot of people unnecessarily

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#52 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWleirjmDoSXdk5MjE9r6G3TjqrdXQFks5rBEujgaJpZM4K6VV5
.

[davidmarkclements]

cf - https://twitter.com/davidmarkclem/status/801896080002711552

[mcollina]

Not needed, deprecation was reversed in core.