Hacker News Reader

I have had a failed heroku deployment because of yarn 1.0 yesterday - quite interesting. Made me define the yarn version in package.json. I have also had some problems with the yarn repo being unavailable a couple of months ago.

That being said - I have migrated to it completely on all projects and never looked back - so yay for yarn!

View on HN

We have patched that issue and already tagged 1.0.1 ;)

See https://github.com/yarnpkg/yarn/issues/4320

Looks like its still having problems on Heroku

https://github.com/heroku/heroku-buildpack-nodejs/issues/468

My heroku deploy succeeded, but my CircleCI run failed for the same reason. Had to upgrade package.json as well, since my circleci build downloads yarn each time. Probably not the most efficient way of doing this but it worked...

Reply on news.ycombinator.com