Log output now printed to stdout. about ipfs-deploy HOT 4 CLOSED

Yes, that is what stderr is for. It is for human readable output.

For example when you install packages and smilar npx writes the logs to stderr so that something like npx sometool >result will properly store the output of tool, the the logs and errors of npx itself. Many tools work like this for example nix-build will write the logs to stderr and the result path to stdout. That is why there are two output streams. There is one for the output of the program (which in this case appear to just be the hash) and another stream for helpful messages such as logs and errors.

Basically stdout is for robots (and humans too) and stderr is for humans.

from ipfs-deploy.

Here's a PR: #216

Thanks for explaining this!

from ipfs-deploy.

Side note: A workaround is using -q to disable the logs, however it is a shame to lose the logs.

from ipfs-deploy.

Hmm, indeed. I really didn't know we should write logs and messages to stderr and thought stdout should be the default. I searched the Internet and it seems there's mixed opinions regarding that. Is there any particular reason why informative logs should be on the stderr? I guess if we consider them debugging, yes.

I can make a PR for this soon.

from ipfs-deploy.