✨ New Feature: Add for support for STDIN/STDOUT workflow

[markstos]

Fixes #10.

QA Log

• Tested both the STDIN and STDOUT features manually.

[markstos]

This has a bug. It is reading from STDIN immediately, so if there's a pause in the pipeline, for example for annotate an image in swappy, it fails. Here's an example to that fails right now:

grimshot save area - | swappy -f - --output-file - | squoosh-filter | wl-copy -t image/jpeg

What's squoosh-filter? It wraps enabling both STDIN and STDOUT support as well some default filter options.

#!/bin/sh
# Expects image on STDIN, prints optimized JPEG to stdout
squoosh-cli --stdout --mozjpeg '{"quality":75,"baseline":false,"arithmetic":false,"progressive":true,"optimize_coding":true,"smoothing":0,"color_space":3,"quant_table":3,"trellis_multipass":false,"trellis_opt_zero":false,"trellis_opt_table":false,"trellis_loops":1,"auto_subsample":true,"chroma_subsample":2,"separate_chroma_quality":false,"chroma_quality":75}' -

I think the fix is to update the code to wait for STDIN to be closed before reading the file. Looking.

[aggregate1166877]

I think the fix is to update the code to wait for STDIN to be closed before reading the file. Looking.

Thank you for the effort. Will wait to hear from you before testing / merging.

I don't know if this helps, but my understanding is that Node handles pipes in odd ways - there was a discussion on the topic here:

• Second child process doesn't receive data when using the stdout of first child process as stdin of second nodejs/node#9413

The bottom two comments are probably the most relevant.