Yarn is a package manager for your code. It allows you to use and share code with other developers from around the world. Yarn does this quickly, securely, and reliably so you don’t ever have to worry.
Hosted by:
Who chose the name YARN, why; and as someone has asked it already, why did you choose the Cat as an emblem?
What is the story on using a whole lot of emojis in the CLI? 😹
I've read the advice to put yarn.lock under version control; for it helps to maintain the same structure of node_modules for every system. npm has shrinkwrap, how would you say is it different from yarn.lock?
As opposed to NPM’s nested dependency model YARN has a flat dependency model. Does this mean there is not a single case where there would be a duplication in the packages, right? Is this always a good thing to have?
Why do the Windows version of YARN doesn’t come with emojis? No ❤ for Windows, eh?
I’ve read that YARN caches copies of packages for offline installs, can you give a brief on how YARN does this under the hood?
Yehuda Katz had written a wonderful article on why he chose to start work on YARN. When did he first approach you, or did you approach him? While you’re at it, can we know the exact history of YARN?
What influenced add over install it was the biggest barrier to switchover for me.. my muscle memory always goes for npm i package -D
Is yarn a temporary solution to a problem (flattened packages, lock files) or do you see it as the next package manager?
I ask because we don't want to put energy into yarn if it's just keeping the seat warm for npm to take the attention back.
I have been coding JS for a long time now. Worked with a fee framworks too. When i code in react eco system i feel i write hardly 20% of my code rest all i just consume from NPM o YARN libraries. I hardly know my system's basic! Should that worry me?
Congratulations on raising your $10MM seed round! What are you doing with that money?
It seems yarn is more focused on project sandboxing like bundler or virtualenv versus package management like rubygems or pip. This is made evident by design around yarn global * and lack of the same configurability currently present in the rival npm client.
Is this inferred roadmap intentional? What are your thoughts on focusing upon the sandboxing problem versus an overall better client for npmjs.org?
Inspired by the question from @kiknag ... Who should not use Yarn because of the difference between Yarn and npm?
If npm adds version locks in the future, would you consider Yarn less useful? Or you want it be different from npm?
Why build a new system rather than push for changes in npm itself? There's plenty of speculation out there, but perhaps you could talk about how Yarn got started; or generally how that kind of decision plays out at facebook? (that is - ramping up an open source project of this scope and potential scale is not a trivial undertaking, how did you decide it was the right way forward?)
What are your relations with the npm team? How did they react?
Ultimately we (developers) don't want to have to handle two package managers, how do you see the future of yarn versus npm? Do you have a plan?
Yarn is great and speeds up npm install times drastically! However, within the first few hours of the official release yarn issues came pouring in to the tune of >380 today. What is the yarn team doing to address those issues quickly? Is there any timeline for releases?
Also, has there been any discussion around adding yarn's caching functionality or parallel install into npm core? What do you see as the future of yarn and npm? Thank you!
That answer leads well into my next question then....
Yarn is a drop in replacement today for npm's package.json. Is the ongoing strategy going to be keeping yarn and npm in sync with package.json structure?
In other words, if the next version of npm updates the structure of node_modules or package.json, will yarn still move to be compatible with it?
Christoph Pojer
Konstantin Raev
Anwesh Mishra
thefootbook.in
why the name yarn as there is already a yarn job scheduler which is an important part of hadoop.