Yarn 1.0: Workspaces, auto-merging lockfiles, selective versions resolutions

Re:Yarn 1.0: Workspaces, auto-merging lockfiles, selective v... by adamgiacomelli on Thursday September 07, 2017 @11:35AM (#15192800)

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!

[ Parent | on HN ]

Re:Yarn 1.0: Workspaces, auto-merging lockfiles, selective v... by BYK on Thursday September 07, 2017 @11:36AM (#15192804)

We have patched that issue and already tagged 1.0.1 ;)

[ Parent | on HN ]

Re:Yarn 1.0: Workspaces, auto-merging lockfiles, selective v... by BYK on Thursday September 07, 2017 @11:36AM (#15192813)

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

[ Parent | on HN ]

Re:Yarn 1.0: Workspaces, auto-merging lockfiles, selective v... by tarr11 on Thursday September 07, 2017 @03:40PM (#15195047)

Looks like its still having problems on Heroku

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

[ Parent | on HN ]

Re:Yarn 1.0: Workspaces, auto-merging lockfiles, selective v... by tarr11 on Thursday September 07, 2017 @01:18PM (#15193866)

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...

[ Parent | on HN ]