Hacker News Reader

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 examples use npm, but I have seen a lot of new projects to go with Yarn. Is this battle yet decided?

View on HN

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.

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.

The gap has closed but afaik yarn is sill a bit faster

Reply on news.ycombinator.com