News for hackers. Stuff that matters.
Re:Yarn – A new package manager for JavaScript by andreygrehov on Tuesday October 11, 2016 @11:52AM (#12685523)
I just tried to install yarn and ran it to against a relatively large React application. What's interesting is that it found an incompatible module and could not proceed, whilst npm works fine.

The article states that running `yarn` is the same as `npm install`, which doesn't look like the case. At that point, I'm curious what are the differences.

Re:Yarn – A new package manager for JavaScript by thejameskyle on Tuesday October 11, 2016 @11:55AM (#12685561)
Sorry about that, there are very likely still some bugs out there we weren't able to catch in all our testing which will be ironed out by the community in the next few days. Can you open an issue with details about which package failed to install? https://github.com/yarnpkg/yarn/issues/new
Re:Yarn – A new package manager for JavaScript by andreygrehov on Tuesday October 11, 2016 @12:12PM (#12685743)
Thank you. Done. The issue is reproducible with an entirely new project.
Re:Yarn – A new package manager for JavaScript by steveklabnik on Tuesday October 11, 2016 @12:15PM (#12685781)
A fun side effect of reproducible builds: recreating bugs for bug reports is easier.
Re:Yarn – A new package manager for JavaScript by quarterto on Tuesday October 11, 2016 @12:00PM (#12685624)
npm treats the package.json engines field as advisory, but yarn is strict about it. maybe that's you're problem