| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
+1 to making it public, but I don't think tty is the best place to put it. Perhaps util would be better? |
Sorry, something went wrong.
|
I don't want to bloat util, but I think it makes more sense. |
Sorry, something went wrong.
With moving in the direction of deprecating process.binding, it makes sense to expose the ability to guess the handle type of an fd.
|
Ok, changed to util |
Sorry, something went wrong.
|
Has anyone actually asked for this? I know the debug module uses tty_wrap.guessHandleType() but that's because it copied createWritableStdioStream() from src/node.js wholesale. |
Sorry, something went wrong.
|
Not to my knowledge. Just wanted to take some proactive steps to when we actually deprecate process.binding |
Sorry, something went wrong.
|
Okay, in that case I'm -1 until a reasonable use case pops up. Adding an API is easy but if it turns out to be the wrong API, we're stuck with it. Proactivity is what got us the util.is*() functions. |
Sorry, something went wrong.
|
Fair enough |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
With moving in the direction of deprecating process.binding,
it makes sense to expose the ability to guess the handle type
of an fd.
Does it make sense that this is exposed in tty?
An example of where this would be useful is debug which
is a quite popular package. (https://github.com/visionmedia/debug/blob/master/node.js#L144-L203)
Related: #2768