Anyone know what the rationale is here? I use yarn every day but I can’t understand the logic of having two different package managers in the node project. Replacing npm with yarn might be reasonable but I don’t get why you’d want two.
According to the PR, it's "meant to improve the experience of new users." Basically, I think this is trying to get around the situation where you have to run `npm install -g yarn` before you can run `yarn install`.
2 comments
[ 3.5 ms ] story [ 12.2 ms ] thread