When I run yarn on my project, I get a warning during the linking phase stating:
warning " > foo@1.0.0" has incorrect peer dependency "bar@^2.0.0"
After going through and cleaning these warnings up, I would like to prevent future regressions like this by making these fail the install step in our dev and CI environments. Does yarn provide any mechanism to do this (i.e. CLI arguments or config file changes) or do I need to write something to parse the output?