Debug: RFC: 3.0 stdout moved off of APIs that are pending removal
It was never documented and was supposed to be internal.
Used at node.js#L164.
ChALkeR
All 8 comments
lets discuss here
thebigredgeek
on 26 Dec 2016
I'm not quite sure what's going on with the «won't fix»/reopening/renaming and the proposed discussion, but I do have a quick question — does that line get called for a significant amount of debug users or not?
ChALkeR
on 30 Dec 2016
@ChALkeR We're going to remove the offending code. Please see #406.
TooTallNate
on 30 Dec 2016
@TooTallNate Thanks. Could you clarify for what usecases was that line called? Only when DEBUG_FD was set to something other than 1 and 2, or for something even more specific?
ChALkeR
on 3 Jan 2017
Correct, only when DEBUG_FD was something other than 1 or 2, which was a very low number people (in any...). I've never used it.
TooTallNate
on 3 Jan 2017
@ChALkeR That said, even though debug no longer will use createWritableStdioStream(), it would be nice if Node.js exposed that kind of thing for other use-cases.
TooTallNate
on 3 Jan 2017
Gonna close this btw, since the relevant PRs have been merged at this point.
TooTallNate
on 3 Jan 2017
Sgtm
thebigredgeek
on 3 Jan 2017
Related issues
xkubow
·
4Comments
krismeister
·
6Comments
ibc
·
5Comments
dave-ops
·
6Comments
fforres
·
7Comments
Most helpful comment
@ChALkeR We're going to remove the offending code. Please see #406.