Do not write entire contents of yarn.lock to yarn-error.log

Do you want to request a feature or report a bug?

Feature?

What is the current behavior?

  1. Run anything that produces an error, e.g. yarn thiscommanddoesnotexist
  2. yarn-error.log is written with the entire contents of yarn.lock copied to it.

What is the expected behavior?
I’m not sure how useful it is to just copy both package.json and yarn.lock into the error log, especially in the javascript ecosystem where there are an insane amount of (sub-)dependencies.

Please mention your node.js, yarn and operating system version.
Node 9, Yarn 1.5.1, Windows 10.

Author: Fantashit

1 thought on “Do not write entire contents of yarn.lock to yarn-error.log

  1. I find it really noisy and unhelpful to put the yarn.lock into the error log, personally. This is amplified when using lerna + yarn workspaces, where it creates a yarn-error.log file in every package directory.

    Would it be better to allow this to be configurable with an env var?

Comments are closed.