title: What is the difference between npm 3 vs Bower?
body: <p>With npm 3 coming with a flat(-ish) dependency structure, do we use Bower in future or just npm 3 when its released ?</p>
  <blockquote>
  <p>npm is most commonly used for managing Node.js modules, but it works for the front-end too when combined with Browserify and/or $ npm dedupe.</p>
  <p>Bower is created solely for the front-end and is optimized with that
  in mind. The biggest difference is that npm does nested dependency
  tree (size heavy) while Bower requires a flat dependency tree (puts
  the burden of dependency resolution on the user)</p>
  </blockquote>
  <p><a href="https://github.com/bower/bower/issues/1520" rel="noreferrer">merge bower into npm</a></p>
  <p><a href="http://blog.npmjs.org/post/122450408965/npm-weekly-20-npm-3-is-here-ish" rel="noreferrer">npm3</a></p>
  <p><a href="http://blog.npmjs.org/post/101775448305/npm-and-front-end-packaging" rel="noreferrer">npm-and-front-end-packaging</a></p>