Everything You Wanted to Know About Yarn Package Manager

This post contains content that is plagiarized verbatim from other sources. Namely Yehuda's blog post and the Yarn homepage itself.

- promises &quot;everything you wanted to know about yarn&quot;<p>- has barely any content

I have such a burning, unquenchable hatred for NPM that I just switched to using Yarn. It&#x27;s fine, has done what I expect it to, and hasn&#x27;t caused any problems so far. Maybe not an ideal solution, but for someone coming primarily from languages that have non-shitty package managers it&#x27;s a breath of fresh air.

Yarn needs to learn from lein for clojure. Yarn is the wrong way forward, but an incremental fix for npm.

What&#x27;s the benefit of having a lockfile compared to just specifying exact versions in your package.json?

anyone knows if yarn has an equivalent of --no-bin-links option?<p>EDIT: guess not according to <a href="https:&#x2F;&#x2F;github.com&#x2F;yarnpkg&#x2F;yarn&#x2F;issues&#x2F;929" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;yarnpkg&#x2F;yarn&#x2F;issues&#x2F;929</a>

Why can&#x27;t all of this be patched in npm ? Why do we have to create a new tool every time ?<p>It makes no sense and honestly makes me want to tear my hairs.