Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DeprecationWarnings are written out on the console #35

Open
mikaelkaron opened this issue Feb 23, 2017 · 3 comments
Open

DeprecationWarnings are written out on the console #35

mikaelkaron opened this issue Feb 23, 2017 · 3 comments

Comments

@mikaelkaron
Copy link
Contributor

mikaelkaron commented Feb 23, 2017

When running a hook with deprecated api usage you can see:

(node:13604) DeprecationWarning: Using Buffer without `new` will soon stop working. Use `new Buffer()`, or preferably `Buffer.from()`,
 `Buffer.allocUnsafe()` or `Buffer.alloc()` instead.

if you try to use a package like trumpet things get even weirder.

Possible solutions would be to somehow set the process the same way as passing --no-deprecation in the cli, perhaps nodejs/node@c6656db can shed some light on that.

@Marak
Copy link
Collaborator

Marak commented Feb 24, 2017

Is this because the deprecation warnings are coming over STDERR? Or are they coming from STDOUT?

@mikaelkaron
Copy link
Contributor Author

They are coming over STDERR from what I can see.

@Marak
Copy link
Collaborator

Marak commented Feb 24, 2017

I'll merge this since it will fix the issue.

We may have to migrate the STDERR output code to STDIO 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants