Everything You Wanted to Know About Yarn Package Manager

#1

Post by fizerkhan » Tue, Oct 18, 2016, 1:36 PM UTC

Everything You Wanted to Know About Yarn Package Manager
atatus.com

Re: Everything You Wanted to Know About Yarn Package Manager

#2

Post by gotofritz » Tue, Oct 18, 2016, 3:19 PM UTC

- promises "everything you wanted to know about yarn"

- has barely any content

Re: Everything You Wanted to Know About Yarn Package Manager

#3

Post by ittan » Tue, Oct 18, 2016, 3:19 PM UTC

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

Re: Everything You Wanted to Know About Yarn Package Manager

#4

Post by agnivade » Tue, Oct 18, 2016, 3:22 PM UTC

Why can't all of this be patched in npm ? Why do we have to create a new tool every time ?

It makes no sense and honestly makes me want to tear my hairs.

Re: Everything You Wanted to Know About Yarn Package Manager

#5

Post by ngrilly » Tue, Oct 18, 2016, 3:33 PM UTC

ittan wrote: post #3

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

What can be learnt from lein? (I've not used Clojure enough to know.)

Re: Everything You Wanted to Know About Yarn Package Manager

#6

Post by joelthelion » Tue, Oct 18, 2016, 3:42 PM UTC

gotofritz wrote: post #2

- promises "everything you wanted to know about yarn" - has barely any content

Well, most people don't want to know much about Yarn. Granted, mostly because they don't even know it exists :)

Re: Everything You Wanted to Know About Yarn Package Manager

#7

Post by Touche » Tue, Oct 18, 2016, 3:48 PM UTC

agnivade wrote: post #4

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

A lot of people say this and I'll repeat the answer: go look at npm's source code and tell me you'd like to "patch in" a large change such as the one Yarn takes on.

No seriously, go look at their source code. In particular go look at the caching code, one of the big things that Yarn fixes. You think their time would have been better spent hacking on that?

Re: Everything You Wanted to Know About Yarn Package Manager

#8

Post by aarpmcgee » Tue, Oct 18, 2016, 3:52 PM UTC

ittan wrote: post #3

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

I would also like to hear more about this!

Re: Everything You Wanted to Know About Yarn Package Manager

#9

Post by jerrycruncher » Tue, Oct 18, 2016, 3:54 PM UTC

agnivade wrote: post #4

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

My favorite thing about the post* that introduced Yarn, itself a rewrite of a basic component, is that the author(s) unironically began with "In the JavaScript community, engineers share hundreds of thousands of pieces of code so we can avoid rewriting basic components, libraries, or frameworks of our own."

*https://code.facebook.com/posts/1840075619545360?_fb_noscrip...

Re: Everything You Wanted to Know About Yarn Package Manager

#10

Post by sotojuan » Tue, Oct 18, 2016, 3:55 PM UTC

agnivade wrote: post #4

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

I don't get why people say this. You're acting like the npm team is desperate for contributions and fixes and the Yarn people are like "No! We'll make our OWN tool!".

It's the literal opposite. npm hasn't been open to contributions or fixes for years.