title: Can yarn be considered a viable option as a replacement for bower and npm?
body: <p>I should clarify that I'm not that experienced with front-end tools, so I'm sorry in advance if I'm asking something obvious and stupid.</p>
  <p>So far I've been using bower for front-end and npm for server-side, although each of the tools mentioned has its advantages and by that I mean <em>flat dependency management</em> of <strong>bower</strong> (reduces load from the client) and <em>nested dependency management</em> of <strong>npm</strong> (helps with versioning), it has become quite cumbersome to use so many tools (webpack, browserify, etc.). I may've been using these tools the wrong way and could've used either of them with some option (not known to me) and have been only scratching the surface, I just took this <a href="https://stackoverflow.com/questions/18641899/what-is-the-difference-between-bower-and-npm#answer-18652918">answer</a> as my rule of thumb and have been doing so ever since I've read it. It would be great if I could reduce at least these two to one.</p>
  <p>Lately I've become curious about yarn and with all the hype around it, it seems as if it has been doing a good job and as if it will replace npm completely. As I've read the docs I've discovered the --flat option and that made me wonder if it would be possible to use it as bower replacement as well? If so, does it mean I could have either flat or nested dependency manager (by just having multiple JSON files for back- and front-end)?</p>
  <p>I would really appreciate if someone could point me in the right direction!</p>