3 ms·

And if you are using npm & bower in the same project then this other issue is a show stopper https://github.com/yarnpkg/yarn/issues/616 https://github.com/yarnp

• ceejayoz 10y ago
  Out of curiosity, why use npm and bower in the same project?
  • joshstrange 10y ago
    Not op but I'll chime in. My team uses npm for our build tools and bower for our frontend libraries (moment, chats, lodash, etc). Our re-write only uses npm but at the time (and possibly even now) there were frontend libraries that only provide bower packages and bower seemed like the right tool for the job anyways.
    • gotofritz 10y ago
      It doesn't sound ideal having two tools that do pretty much the same thing, you are just adding a potential extra point of failure. Migrating from bower to npm is incredibly easy.
      • Sacho 10y ago
        How would you migrate libraries that are only on bower, not npm?
        • ceejayoz 10y ago
          How many of those are a) left and b) still maintained?
        • gotofritz 10y ago
          If there are still any in 2016 it's a good sign they are not begin actively maintained
      • ferentchak 10y ago
        I remember wondering this same thing myself when Bower was the the new hotness. "Don't I already have a tool that does exactly this?"