I don't have any real experience with it. But it sure is fast and easy. I am not going to use it as my primary JS package manager just yet though. I am not sure if it will survive and adoption will keep increasing after the initial hype has faded away.
I wouldn't jump right into it if it's for production and right now I don't have time to play around so for me it's a no. I think for anyone it's way too early to impelement in production since it only came out a week ago or so, it's no fun to add something to a production code which will be obsolete very quickly.
Hi,
I try yarn and my experience was good. Is easy to use but it doesn't replace npm at all. A nice thing of yarn it's the lock file and caching libraries for offline instalation.
Denny Trebbin
Lead Fullstack Developer. Experimenting with bleeding-edge tech. Irregularly DJ. Hobby drone pilot. Amateur photographer.
brew install yarnon macOS or Linux.choco install yarnon Windows.With those external installations, you have
yarnready and functioning without interfering your currentnodeinstallation - except you've installed node directly viabrew. Also no need to migrate globals when upgradingnodevia any node version manager.Then the rest works just like it does with
npm.mkdir supercoolsomething cd supercoolsomething git init git add remote origin something yarn init yarn add react@15.4.0-rc.4 yarn add babel@latest yarn add runjsThe generated
package.jsonlooks familiar, just like we know it fromnpm.The installation of packages is fast and produce the same
node_modulesstructure on every other machine - except on different operating systems.What I noticed is, that
yarnaccesses its registry atregistry.yarnpkg.con. You may need to add an exception to your firewall or proxy.It's ready for production now; because
yarnisn't bloody fresh code just released a week ago or so.yarnis the product of a corporation between Facebook, Exponent, Google, and Tilde.