`process.stderr` and `process.stdout` are unlike other streams in Node.js in
that they cannot be closed (`end()` will throw), they never emit the `finish`
-event and that writes are usually blocking.
-
-- They are blocking in the case that they refer to regular files or TTY file
- descriptors.
-- In the case they refer to pipes:
- - They are blocking in Linux/Unix.
- - They are non-blocking like other streams in Windows.
+event and that writes are always blocking.
To check if Node.js is being run in a TTY context, read the `isTTY` property
on `process.stderr`, `process.stdout`, or `process.stdin`:
<!--type=misc-->
Both Writable and Readable streams will buffer data on an internal
-object called `_writableState.buffer` or `_readableState.buffer`,
-respectively.
+object which can be retrieved from `_writableState.getBuffer()` or
+`_readableState.buffer`, respectively.
The amount of data that will potentially be buffered depends on the
`highWaterMark` option which is passed into the constructor.