[mathiasrw]

Closes #839

Stacked on #838.

Change

When the reader of a pipe stops early, like head, nobody reads the rest, and that is fine. Before, the run crashed with EPIPE and a stack trace, and exit code 1:

> rexreplace foo bar big.txt -o | head -1
1 bar
EPIPE: broken pipe, write
…

Now the run ends as usual, with no error, on Bun and on Node:

• Bun throws when a closed pipe is written to, and Node gives an error event, so both are caught. All other errors are thrown as before.
• After that, nothing more is written to that stream.
• The status report goes through the same write, so -d | head -1 is fine too.

Tests

test/fix/839.test.js is new. It pipes 200,000 lines into head -1, also with the status report, and fails without the fix. yarn test-ci passes.

Also closes #852

Follow-up

The detail of an error, like the file, is now on its own line under the message, for every error:

 ❌ File not found
    a.md