3 ms·

I have been a web dev 25 years. It is nice to see JavaScript based backends mature. One day we will have Ruby on Rails or Django of JavaScript world :) Next.js

• Toddward 7y ago
  The npm client largely resolved the issues Yarn was created to solve. I used Yarn for a while, but eventually switched all my projects back to npm.
  • 33degrees 7y ago
    The gap has closed but afaik yarn is sill a bit faster
• CSSer 7y ago
  To answer your question: in terms of optimization, yes. Npm has pretty much closed the gap. However, depending on your package management strategy, I’d go with Yarn until/unless npm offers a better solution for monorepo package management. Npm currently forces you to more or less manually manage symlinks, which can be painful. Yarn workspaces on the other hand, although it does require some ritual, seems to just work.