Open mikaelkaron opened 7 years ago
Is this because the deprecation warnings are coming over STDERR? Or are they coming from STDOUT?
They are coming over STDERR from what I can see.
I'll merge this since it will fix the issue.
We may have to migrate the STDERR output code to STDIO 3.
When running a hook with deprecated api usage you can see:
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@c6656db352973d6aea24cb1a3c76adf042b25446 can shed some light on that.