IMO yarn was a protest movement when npm wasn't adding the features devs wanted. npm5 is the direct result and yarn should pat itself on the back and bow out to avoid fragmenting the community.
Why should yarn bow out? Correct me if I'm wrong, but the yarn project didn't do the following: - put a pre-release build under a tag that looks like a normal build without a pre suffix - had documentation that expressed sudo as an acceptable way to do things to end users - then had a bug which torched machines if they ran any npm command under sudo. (which you shouldn't do anyway, but see point 2) - when pushing the fix, put hashtags in the announcements with a distinct tone of blame towards the end users.
This was the famous "rm -Rf /" bug.
> put hashtags in the announcements with a distinct tone of blame towards the end users.
What are you referring to?
Probably this: https://blog.npmjs.org/post/171169301000/v571
No thanks. NPM caused the usability and feature problems first and there's no reason it won't happen again if there was no competition. Yarn is still better overall and I'm much rather they stick around.
Also, I think npm released it's lockfile too quickly. It didn't work for quite a while. Maybe it does now, I don't know, because any npm projects I have I have turned off package-lock due to it not working in the past. Yarn's lockfile just works, and always has.
So I'll stick with Yarn as long as they just keep it stable the way it is.