Consistently use yarn or npm across docs

[m-allanson]

Across Gatsby's docs both yarn and npm are used interchangeably, which seems a bit confusing. The docs should consistently mention either yarn or npm. Or both?

[KyleAMathews]

I always use NPM — but yeah, we should standardize that and fix anyone's any uses of Yarn.

[giladronat]

@KyleAMathews I’d gladly make it all consistent and PR -- do you prefer standardizing to NPM because you use it or Yarn because it’s probably more common?

[shannonbux]

good question @giladronat and thanks for offering. @m-allanson I've wondered the same thing and been too new to know if I'm just missing something or if there are reasons for npm vs. yarn.

[shannonbux]

And then I accidentally closed and opened this again haha. Still a github newb.

[KyleAMathews]

@giladronat yeah NPM cause it's the default and anyone using Yarn is already familiar with translating instructions to Yarn. Thanks!

[giladronat]

@KyleAMathews that makes sense. As a JS newbie that was recommended Yarn by friends, I don’t fall into that category, but I don’t know if I’m a representative sample. I’ll change to NPM though; most of the work is just finding all instances, not changing one way or another 😄
Edit: even as a newbie I’m actually able to figure it out, so NPM is probably best.

[webrune-tim]

I am happy to help go through the docs looking for yarn and npn. Which do you prefer? I can update it.

[m-allanson]

Thanks @giladronat!

And thanks @WebRuin too, but it looks like @giladronat is working on this one already.

[giladronat]

This is done. Feel free to close @KyleAMathews

[KyleAMathews]

Thanks @giladronat!

[eballeste]

i personally use npm but anytime i start a new gatsby project with gatsby new it automatically uses yarn in it's install process and throws an npm related warning:

warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.

it also creates a yarn lock file in addition to the package-lock.json