Hi! This is not an issue with lerna, but rather just a question about lerna's recent move from yarn to npm, and the lerna team's recommendation for other projects going forward.

At my company, we've been using parts of lerna internally in our build tools for its change detection and publishing primarily, but we're also investigating migrating some of our projects into a monorepo structure. As part of this, I'd been planning on moving us over to yarn from npm@5 as well, primarily for reliability and speed improvements.

However, I noticed that recently, lerna has moved from yarn back to npm with this commit, and in this comment you've mentioned running into significant edge-case bugs with yarn.

So if you've got some free time and are happy to discuss, I was just interested in your reasonings for moving back to npm, and how the latest npm@5 compares to yarn (especially in light of yarn workspaces).