Open mgol opened 7 years ago
This breaks any script which expects formatted output on stdout.
I second this proposal.
Outputting to stdout breaks generally expected command-line behavior, e.g. if you run...
yarn webpack --profile --json > profile.json
profile.json will contain some yarn debug information at the top and bottom of a 90MB JSON file.
Indeed, this current violation is a violation of the UNIX way which expects tools to be composable via pipelines.
yes please
Do you want to request a feature or report a bug?
A bug (I think).
What is the current behavior?
Yarn prints everything to stdout, including debugging info not related to the command output.
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
I'd expect the above output to appear only if we skip the redirection (
2>/dev/null
). Otherwise, I'd like it to behave like that:This is also how npm behaves (tried with npm 3.10.9):
Please mention your node.js, yarn and operating system version.
Node.js 6.9.2, yarn 0.18.0, macOS 10.12.1 (16B2555)