docs(tutorial): tutorial/part-three -> walkthrough failing if yarn is selected as packageManager

Summary

when the packageManager in ~/.config/gatsby/config.json set to yarn then the walkthrough failing (see related issues)

Basic example

Possible changes and enhancements:

• warning, when yarn is selected as packageManager but a package-lock.json exists and is newer than the yarn.lock
• allow to set the packageManager per project folder
• add a hint to the tutorial to try yarn?

… other ideas?

Motivation

no error while walkthrough

related Issues

• #6834 gatsby develop is not working after npm install
• #20225 Failed to 'gatsby develop' after installing typography plugin
• #21989 chore(cli): gatsby info and gatsby --version should print which packageManager used
• #19827 Ambiguous "StoreStateProvider" error for all gatsby commands

[nicopresto]

Interesting, my walkthrough failed in tutorial three when I was npm installing the typography kit. Not sure if it relates to this. NPM was my main install however. Were you running windows by ay chance?

My walkthrough also failed in tutorial three when using npm install for typography, but was successful with yarn: yarn add gatsby-plugin-typography react-typography typography typography-theme-fairy-gates

[jonniebigodes]

@muescha i was going over this and it seems that the middle one could be the way to go.

When the user installs the cli globally he has the option to set the package manager. When he uses the cli it will default to the one set at the time of installation. But like other CLI’s that exist something like CRA and the vue cli they allow you to initialize the project with package manager of choice through a flag or option-

More even that there’s probably some users that installed yarn at some point but never get around it, or haven’t shifted to their mental model, also after doing a quick check on the documentation, more specifically the tutorial tends to use npm instead of yarn.