What are your relations with the npm team? How did they react?
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!
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?
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?)
Why should I use Yarn instead of NPM?
The fact that Yarn is built by brilliant heads from giant companies is enough to make us look into it, but how does yarn tackle security issues while loading dependencies. "npm allows scripts to run while installing dependencies".How does Yarn Solve that ?
First of all, congratulations, team. Yarn's performance boost alone worths everything.
But before starting develop yarn, did you talk with npm's team about opensourcing/work with the npm and inprove it?
Why is Yarn called Micro Secure?
Congratulations on raising your $10MM seed round! What are you doing with that money?
install it was the biggest barrier to switchover for me.. my muscle memory always goes for
npm i package -D
Where did the name 'Yarn' come from?
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.
why the name yarn as there is already a yarn job scheduler which is an important part of hadoop.
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?
If npm adds version locks in the future, would you consider Yarn less useful? Or you want it be different from npm?
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?
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?
What OS & browser do you guys use at Facebook for day-to-day development works?
Why do the Windows version of YARN doesn’t come with emojis? No ❤ for Windows, eh?
Does YARN have any effect on how it handles node module registries?
What does YARN’s roadmap look like?
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?
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?
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? 😹