Using yarn instead of npm according to the paragraph above it

[felixsanz]

Got some code for us? Awesome 🎊!

Please include a description of your change & check your PR against this list, thanks!

• Commit message has a short title & issue references
• Commits are squashed
• The build will pass (run npm test).

More info can be found by clicking the "guidelines for contributing" link above.

[kevinansfield]

@felixsanz thanks for taking the time to check the docs 😄 npm run and yarn run will do (mostly? we haven't tested so didn't want to update yet) the same thing. I had intentionally left it as npm run so that we're using the same script runner as our non-developer docs, we're only using yarn for dependency management right now.

[kirrg001]

Hmmm from my perspective it would be correct to accept this change, because the init command is already using yarn. And as @kevinansfield said, they are doing the same. I think it's less confusing if we switch to yarn run init.

[kevinansfield]

👍 fine with me if everything works

[kirrg001]

@felixsanz Could you please rebase? Thank you!

[kirrg001]

@felixsanz ping

[kirrg001]

Closing in favour of #8475, thanks again 👋