Someone was puzzled as to why their Node command was cutting off output when piped to another command. After some investigation, they discovered that the pipe capacity is actually 65,536 bytes on POSIX systems, creating a limit that was causing the issue. This unexpected limitation led to a deep dive into the inner workings of Node.js streams and the asynchronous behavior of writing to pipes. The culprit was found to be the blocking of the event loop when writing to a full pipe, causing data to be cut off. By understanding this behavior and utilizing the drain event, the issue was resolved, showcasing the complexity and nuances of stream buffering in Node.js.
https://sxlijin.github.io/2024-10-09-node-stdout-disappearing-bytes