Gary Green

I think a different PR attempted to fix this better: https://github.com/laravel/framework/pull/40306 It's really an issue with HOW the middlewares are defined. By defining the middlewares in the construct Laravel HAS...

This is something that should be a package used as part of app deployment flow, if people have any use for it. Few fundamental issues come to mind with this:...

> i would rather allow to produce result on stdout when input was from stdin. How would that work? Do you mean not have a public option `--stdout` and instead...

Added use case for the PR.

In reference to multiple files - this isn't something I am particularly interested in adding support for, as I'm primarily focused on improving the use case as described above. To...

It's worth noting that nearly all unix utilities/tools have a limitation of being only able to work on one file as stdin -> stdout (with some exceptions). However, piping is...

> * don't touch stderr. any content there is good content we want to still have. it's not stdout Would the contents of that error message form part of the...

> * cache was used and it says to not do this file This PR doesn't change anything to do with the cache. So it works exactly the way it...

> * yes, on OS level you say which stream you are grabbing, by default you grab only stdout, not stderr In which case, shall I change it to still...

Ohhh look, Google's Brotli CLI tool does `--stdout` even though it supports multiple files.  😸