Miss Dada  🏳️‍⚧️

The context here is: I have a test runner. When a test fails, it does `process.exit(1)`. But that means that any failing test that prints a lot of data to stdout or stderr will have some of it silently truncated. And it only happens sometimes.

This is really blowing my mind. "Send things across a pipe when they're written to stdout" is one of the most fundamental Unix things, but Node can't do it. Yet it was marketed as being Unixy from the very beginning.

What is Unixy is: blocking IO.

Three hours in. Still doesn't work. I first used a Unix in 96 or 97. I've never seen anything break stdout like this.

Is there no explicit flush method to call?

nope

I'm sure there's a long discussion with reasoning and tradeoffs out there, but I'm baffled at how a language could have non-blocking/buffered IO by default and not make flushing part of the required API